Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddb6a38740b4a47ea5d842d12ae0ac416af5752180f25bbc72ab58b705a22f8a

Tx prefix hash: 5f88db16aeb489f6b2f1608132275dbbd7093832ae98b5e50b6a55a5464dd5b9
Tx public key: f7bbdf2fed3f504a3bd7ecd6f835ff12388bfec5f6898ccc3e785a2a5bce7391
Timestamp: 1729419379 Timestamp [UCT]: 2024-10-20 10:16:19 Age [y:d:h:m:s]: 00:210:23:11:41
Block: 1135643 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 150578 RingCT/type: yes/0
Extra: 01f7bbdf2fed3f504a3bd7ecd6f835ff12388bfec5f6898ccc3e785a2a5bce7391021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1adcd2b659d2070a8865b49e2af81d37b0db3fa17e9b58fde20cf34d3e870558 0.600000000000 1618982 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": 1135653, "vin": [ { "gen": { "height": 1135643 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1adcd2b659d2070a8865b49e2af81d37b0db3fa17e9b58fde20cf34d3e870558" } } ], "extra": [ 1, 247, 187, 223, 47, 237, 63, 80, 74, 59, 215, 236, 214, 248, 53, 255, 18, 56, 139, 254, 197, 246, 137, 140, 204, 62, 120, 90, 42, 91, 206, 115, 145, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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