Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 971a141995f6188efd593dbcedd00c7a03a292d933bb1d24035b7ec63876e339

Tx prefix hash: 54cb4641c3147e1f1ad9278b15eb76c699a513ecd87ed029d12845cb4b116594
Tx public key: 0387b9cb82c4835867b550bb6e0421a8c0f70a17c3cdfa26a793d32fa116d18a
Timestamp: 1762623982 Timestamp [UCT]: 2025-11-08 17:46:22 Age [y:d:h:m:s]: 00:058:05:07:43
Block: 1407805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41706 RingCT/type: yes/0
Extra: 010387b9cb82c4835867b550bb6e0421a8c0f70a17c3cdfa26a793d32fa116d18a021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28365f523dab2e3f6fd10b612a21e709577cbd1c98e393481fa9d3ce38e046b0 0.600000000000 1896226 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": 1407815, "vin": [ { "gen": { "height": 1407805 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28365f523dab2e3f6fd10b612a21e709577cbd1c98e393481fa9d3ce38e046b0" } } ], "extra": [ 1, 3, 135, 185, 203, 130, 196, 131, 88, 103, 181, 80, 187, 110, 4, 33, 168, 192, 247, 10, 23, 195, 205, 250, 38, 167, 147, 211, 47, 161, 22, 209, 138, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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