Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd0b1f5ba429d945dfc79623bf793ba82684924aebd47a4a92bd68ff8f98e9d2

Tx prefix hash: d64d9bde323101bd8a1cc5a9b60aae08c7328966f2f1c0e4a675d4d178e900d7
Tx public key: 0ac0e2e2d4fc42a837560dd277d98f2c4689d2f241dc5fb2c1670bb9b415423c
Timestamp: 1702535096 Timestamp [UCT]: 2023-12-14 06:24:56 Age [y:d:h:m:s]: 01:155:07:27:15
Block: 912757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 372173 RingCT/type: yes/0
Extra: 010ac0e2e2d4fc42a837560dd277d98f2c4689d2f241dc5fb2c1670bb9b415423c021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d2520c437caedd0f30939f645b74e20ad7fd15fc405c7dd587d63f82f285a52 0.600000000000 1369993 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": 912767, "vin": [ { "gen": { "height": 912757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d2520c437caedd0f30939f645b74e20ad7fd15fc405c7dd587d63f82f285a52" } } ], "extra": [ 1, 10, 192, 226, 226, 212, 252, 66, 168, 55, 86, 13, 210, 119, 217, 143, 44, 70, 137, 210, 242, 65, 220, 95, 178, 193, 103, 11, 185, 180, 21, 66, 60, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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