Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1f62cedb28ca017f48f83d493f4838ec9245694693695ee025229aa7761df8f

Tx prefix hash: 25a70248a278302d35a7d3d2c1b7d3d9fded2a41945057fb0dc90b8a909dcadf
Tx public key: 4c7a94ba71d0f7f8509a14f3d5d3a02e17508024eadb457d326b3690c3f4d709
Timestamp: 1705225493 Timestamp [UCT]: 2024-01-14 09:44:53 Age [y:d:h:m:s]: 01:065:10:08:53
Block: 935059 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307865 RingCT/type: yes/0
Extra: 014c7a94ba71d0f7f8509a14f3d5d3a02e17508024eadb457d326b3690c3f4d70902110000000139e1d5d3000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b95ddbe63516fe8b42476d7966a42d8f4e7ee802a8eb0670b084f632e01e4dc4 0.600000000000 1393075 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": 935069, "vin": [ { "gen": { "height": 935059 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b95ddbe63516fe8b42476d7966a42d8f4e7ee802a8eb0670b084f632e01e4dc4" } } ], "extra": [ 1, 76, 122, 148, 186, 113, 208, 247, 248, 80, 154, 20, 243, 213, 211, 160, 46, 23, 80, 128, 36, 234, 219, 69, 125, 50, 107, 54, 144, 195, 244, 215, 9, 2, 17, 0, 0, 0, 1, 57, 225, 213, 211, 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