Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6e3cf280c956f238fd1215a92379c74826bd430fbb8c844ef8e6f7ba0920e8a7

Tx prefix hash: bf53cb5234766542b543148f1c94a4959c0104d8d9e398601f047662f72ecd16
Tx public key: ac7212190e7e6a02e209fd5bece187950f7c5e52716e19d9d1697991cce7a1b3
Timestamp: 1749546973 Timestamp [UCT]: 2025-06-10 09:16:13 Age [y:d:h:m:s]: 00:161:03:49:13
Block: 1301971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112848 RingCT/type: yes/0
Extra: 01ac7212190e7e6a02e209fd5bece187950f7c5e52716e19d9d1697991cce7a1b302110000000b43846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf2e6a1392bcc39f56a6eef46fb0462ad22b1b0878ae9a43fde60c24aa16be5b 0.600000000000 1789538 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": 1301981, "vin": [ { "gen": { "height": 1301971 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf2e6a1392bcc39f56a6eef46fb0462ad22b1b0878ae9a43fde60c24aa16be5b" } } ], "extra": [ 1, 172, 114, 18, 25, 14, 126, 106, 2, 226, 9, 253, 91, 236, 225, 135, 149, 15, 124, 94, 82, 113, 110, 25, 217, 209, 105, 121, 145, 204, 231, 161, 179, 2, 17, 0, 0, 0, 11, 67, 132, 109, 102, 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