Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dd16c6d64d39174cbdf639bb7def45a5ec9aace24a410bcc17926a7b60e894d

Tx prefix hash: 5bddae18eeed49f093fb132445b9a9366b9e0d38e8798d715c7f622f7ecd2d9c
Tx public key: a015c3d64ae98c9095990f7e19b276e6025a482f4d40452ede37b7d6d3996226
Timestamp: 1719943894 Timestamp [UCT]: 2024-07-02 18:11:34 Age [y:d:h:m:s]: 00:349:17:00:36
Block: 1057087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249832 RingCT/type: yes/0
Extra: 01a015c3d64ae98c9095990f7e19b276e6025a482f4d40452ede37b7d6d39962260211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5fbd3d5b436658e0418db4a36e7cbfae2d915e90fecb74183c71e2907e499aa7 0.600000000000 1527516 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": 1057097, "vin": [ { "gen": { "height": 1057087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5fbd3d5b436658e0418db4a36e7cbfae2d915e90fecb74183c71e2907e499aa7" } } ], "extra": [ 1, 160, 21, 195, 214, 74, 233, 140, 144, 149, 153, 15, 126, 25, 178, 118, 230, 2, 90, 72, 47, 77, 64, 69, 46, 222, 55, 183, 214, 211, 153, 98, 38, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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