Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db2c497970bd9798016b0fcc502f1a1a7cb95d5df499f747a540674a327485f9

Tx prefix hash: 10bff99b60e2042232db3a395985871240530ca8cdd3694e304a94a46a6b1ee8
Tx public key: 3d5b0b95128d5f8dcf4f9c09e471cdad7708040f8436ae950fcd406ce6b7f86d
Timestamp: 1721610718 Timestamp [UCT]: 2024-07-22 01:11:58 Age [y:d:h:m:s]: 00:252:18:45:40
Block: 1070902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180584 RingCT/type: yes/0
Extra: 013d5b0b95128d5f8dcf4f9c09e471cdad7708040f8436ae950fcd406ce6b7f86d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7897ea08b11d9a86ab835928b4385ce90b16f29132def7ac26a213a67e07e850 0.600000000000 1542925 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": 1070912, "vin": [ { "gen": { "height": 1070902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7897ea08b11d9a86ab835928b4385ce90b16f29132def7ac26a213a67e07e850" } } ], "extra": [ 1, 61, 91, 11, 149, 18, 141, 95, 141, 207, 79, 156, 9, 228, 113, 205, 173, 119, 8, 4, 15, 132, 54, 174, 149, 15, 205, 64, 108, 230, 183, 248, 109, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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