Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c8ca506689dada3c3912dbc9020db1f68b431d298728b806a8a0dea45a7a3d7

Tx prefix hash: 10058e481448d3468dcb9b6c6be3435734bcde5b7a3eabdd5ba68e118025854a
Tx public key: 6cd6721f597e7027debcaa0c0c2909d784f01d8aea8ff8b99995f7210f8202ed
Timestamp: 1675213412 Timestamp [UCT]: 2023-02-01 01:03:32 Age [y:d:h:m:s]: 02:120:01:52:35
Block: 687127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607496 RingCT/type: yes/0
Extra: 016cd6721f597e7027debcaa0c0c2909d784f01d8aea8ff8b99995f7210f8202ed0211000000015029cbac000000000000000000

1 output(s) for total of 3.245360464000 dcy

stealth address amount amount idx
00: 0c4afb84d9a25c1c4febe8f71cfb1725e8cb5e84e94948100e1ffe6a770cf628 3.245360464000 1129683 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": 687137, "vin": [ { "gen": { "height": 687127 } } ], "vout": [ { "amount": 3245360464, "target": { "key": "0c4afb84d9a25c1c4febe8f71cfb1725e8cb5e84e94948100e1ffe6a770cf628" } } ], "extra": [ 1, 108, 214, 114, 31, 89, 126, 112, 39, 222, 188, 170, 12, 12, 41, 9, 215, 132, 240, 29, 138, 234, 143, 248, 185, 153, 149, 247, 33, 15, 130, 2, 237, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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