Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdd2841873254790e95bb0816d6d560138882d1ebc2c0fa29b1490dca70681ee

Tx prefix hash: 7224033ddcc40e7d16129ccbe939162cffa68ac060f07acf418eab0da7c400c2
Tx public key: 6c48208e4fe145fbb49e0b5d033b503b7581fb8dc5ff0847b95e993f4fae53e3
Timestamp: 1724826433 Timestamp [UCT]: 2024-08-28 06:27:13 Age [y:d:h:m:s]: 00:225:00:53:38
Block: 1097564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160703 RingCT/type: yes/0
Extra: 016c48208e4fe145fbb49e0b5d033b503b7581fb8dc5ff0847b95e993f4fae53e302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3ff8adf8ce0f4af87868f3d981be0e1812a12b41c2619ff5ee3ca84c10bedaa9 0.600000000000 1572965 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": 1097574, "vin": [ { "gen": { "height": 1097564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3ff8adf8ce0f4af87868f3d981be0e1812a12b41c2619ff5ee3ca84c10bedaa9" } } ], "extra": [ 1, 108, 72, 32, 142, 79, 225, 69, 251, 180, 158, 11, 93, 3, 59, 80, 59, 117, 129, 251, 141, 197, 255, 8, 71, 185, 94, 153, 63, 79, 174, 83, 227, 2, 17, 0, 0, 0, 3, 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