Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 6df4fa609f1a58c73ff775616e3be5ccba8296db0d3aeed16e31e6793006f8ac

Tx prefix hash: c036dbd944cdbdaf598a8b1bc0b93f89f664ab26b541376a3aca0c9972bf62f9
Tx public key: 4373fdfff234b0f1037734f1800a1ba238a7ac38fa5c7ea0097b425317f38780
Timestamp: 1709433008 Timestamp [UCT]: 2024-03-03 02:30:08 Age [y:d:h:m:s]: 00:361:13:59:03
Block: 969956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258533 RingCT/type: yes/0
Extra: 014373fdfff234b0f1037734f1800a1ba238a7ac38fa5c7ea0097b425317f387800211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1bd74eb1efe96a27a44f09855564979483fd596aae314b2bd7ae516eb2e53a5 0.600000000000 1429805 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 969966, "vin": [ { "gen": { "height": 969956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1bd74eb1efe96a27a44f09855564979483fd596aae314b2bd7ae516eb2e53a5" } } ], "extra": [ 1, 67, 115, 253, 255, 242, 52, 176, 241, 3, 119, 52, 241, 128, 10, 27, 162, 56, 167, 172, 56, 250, 92, 126, 160, 9, 123, 66, 83, 23, 243, 135, 128, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8