Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 303a6951091034324206e5797ebfcb6e8a67ce22e0ef130e6656d807367d0919

Tx prefix hash: 38875ac4a87ffd0dc7f4e6a2bb555a1c8e012eb5c36221d6828ee9a186f72993
Tx public key: 00196cd7ca67b51526c04a3e9bb501f7c031e1b2a23e320ce98991d45ecd6f23
Timestamp: 1574350272 Timestamp [UCT]: 2019-11-21 15:31:12 Age [y:d:h:m:s]: 05:009:20:05:33
Block: 13744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1150491 RingCT/type: yes/0
Extra: 0100196cd7ca67b51526c04a3e9bb501f7c031e1b2a23e320ce98991d45ecd6f2302110000000166a80d00000000000000000000

1 output(s) for total of 552.664168754000 dcy

stealth address amount amount idx
00: 1fbb5146fa394eedd3f036294c5ced14576a6b31caf6185ffa2a66ca2668ac22 552.664168754000 16637 of 0

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": 13754, "vin": [ { "gen": { "height": 13744 } } ], "vout": [ { "amount": 552664168754, "target": { "key": "1fbb5146fa394eedd3f036294c5ced14576a6b31caf6185ffa2a66ca2668ac22" } } ], "extra": [ 1, 0, 25, 108, 215, 202, 103, 181, 21, 38, 192, 74, 62, 155, 181, 1, 247, 192, 49, 225, 178, 162, 62, 50, 12, 233, 137, 145, 212, 94, 205, 111, 35, 2, 17, 0, 0, 0, 1, 102, 168, 13, 0, 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