Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765d007fd511e406cc2c521a4b42920109ffd44bc3d5a7def57a292a3641eb79

Tx prefix hash: fe1b35808362a3389ce678b83371935ae0c3c389487d4d09baa29e015da26d05
Tx public key: 584f1d466a19da36843da2c35ed664e6f68d451323e1b81ea55ee3b5f799cbab
Timestamp: 1726798525 Timestamp [UCT]: 2024-09-20 02:15:25 Age [y:d:h:m:s]: 00:189:15:12:30
Block: 1113913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135357 RingCT/type: yes/0
Extra: 01584f1d466a19da36843da2c35ed664e6f68d451323e1b81ea55ee3b5f799cbab02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6f2a6015c3d109f4e0eb4d67cf47b6740acba61bc961fd193532c40dc9c66ba 0.600000000000 1593710 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": 1113923, "vin": [ { "gen": { "height": 1113913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6f2a6015c3d109f4e0eb4d67cf47b6740acba61bc961fd193532c40dc9c66ba" } } ], "extra": [ 1, 88, 79, 29, 70, 106, 25, 218, 54, 132, 61, 162, 195, 94, 214, 100, 230, 246, 141, 69, 19, 35, 225, 184, 30, 165, 94, 227, 181, 247, 153, 203, 171, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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