Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6480081e76f5e1b69af98a3d7640718640b2971d7e2909c9ce5f6948b412e73

Tx prefix hash: 29cc62802c89ced19eaee605cac609aa07499b213be98f5da7345bbea23f8971
Tx public key: 6a1a0b0516dd96293b1099a955d15b11af80c3a33a8a418ed22dff0862c0d773
Timestamp: 1723989370 Timestamp [UCT]: 2024-08-18 13:56:10 Age [y:d:h:m:s]: 01:080:08:05:54
Block: 1090641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315856 RingCT/type: yes/0
Extra: 016a1a0b0516dd96293b1099a955d15b11af80c3a33a8a418ed22dff0862c0d77302110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1ee765b5a8961ebbb5e9ddf70f84dd5602d4641e8025f051035dc9d40144b35c 0.600000000000 1565264 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": 1090651, "vin": [ { "gen": { "height": 1090641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ee765b5a8961ebbb5e9ddf70f84dd5602d4641e8025f051035dc9d40144b35c" } } ], "extra": [ 1, 106, 26, 11, 5, 22, 221, 150, 41, 59, 16, 153, 169, 85, 209, 91, 17, 175, 128, 195, 163, 58, 138, 65, 142, 210, 45, 255, 8, 98, 192, 215, 115, 2, 17, 0, 0, 0, 8, 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