Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53581d59ceb66fe45561b14e2edd6d71bbaab6bf09e6f830615e24f791b21244

Tx prefix hash: 75d7d8537b9b704c90514d4839a7ef8004c5d9a5f83dc617668303fbddc3f7cc
Tx public key: 3f7bd8b1625f7209ca6a00c23139a38b5600cb33497e9788545873a0d35adfda
Timestamp: 1706385649 Timestamp [UCT]: 2024-01-27 20:00:49 Age [y:d:h:m:s]: 02:005:14:47:20
Block: 944660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523614 RingCT/type: yes/0
Extra: 013f7bd8b1625f7209ca6a00c23139a38b5600cb33497e9788545873a0d35adfda02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6be06cb862a1e226db36b2c7301cec47120b4491354c1e71164fb15b1ebbb1c5 0.600000000000 1402946 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": 944670, "vin": [ { "gen": { "height": 944660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6be06cb862a1e226db36b2c7301cec47120b4491354c1e71164fb15b1ebbb1c5" } } ], "extra": [ 1, 63, 123, 216, 177, 98, 95, 114, 9, 202, 106, 0, 194, 49, 57, 163, 139, 86, 0, 203, 51, 73, 126, 151, 136, 84, 88, 115, 160, 211, 90, 223, 218, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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