Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a6412e206599f53ddf1253c486154af0eec4dae0b9c69deef5cce4f5711bae

Tx prefix hash: bc4dac4b9a111585ed7c5d4debcce6391f404b2b5f62ad3e649dad590ada2b9a
Tx public key: 7dc0566f9e8776a87779be1198fe7dc73e604a58b40ea9705548abb9b413fd11
Timestamp: 1708744763 Timestamp [UCT]: 2024-02-24 03:19:23 Age [y:d:h:m:s]: 01:283:09:30:44
Block: 964245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 461331 RingCT/type: yes/0
Extra: 017dc0566f9e8776a87779be1198fe7dc73e604a58b40ea9705548abb9b413fd1102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a28ac0405f66a946d3bf5179bad2ee5e5593179a9c13d58f78ae5bfcf3ceb1b4 0.600000000000 1423974 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": 964255, "vin": [ { "gen": { "height": 964245 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a28ac0405f66a946d3bf5179bad2ee5e5593179a9c13d58f78ae5bfcf3ceb1b4" } } ], "extra": [ 1, 125, 192, 86, 111, 158, 135, 118, 168, 119, 121, 190, 17, 152, 254, 125, 199, 62, 96, 74, 88, 180, 14, 169, 112, 85, 72, 171, 185, 180, 19, 253, 17, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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