Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acf5fb381bf6b9a39f4c2793261be2663c04b185a7885c46ab3d4e1209dcc6e5

Tx prefix hash: 01a364229c5b29327c7f79577380d69dd43795c25e827d84fa8d32c00031c87e
Tx public key: 556daee0d59a6a3990fb280d3c48135fdb133bdaf5eedf9a933e03f28d268cd5
Timestamp: 1726954418 Timestamp [UCT]: 2024-09-21 21:33:38 Age [y:d:h:m:s]: 00:215:14:44:31
Block: 1115213 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153935 RingCT/type: yes/0
Extra: 01556daee0d59a6a3990fb280d3c48135fdb133bdaf5eedf9a933e03f28d268cd502110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f60aad766a198b5c05aa46222a0e4f19e20ebd9e7ba240b97dc0e8764a10ac 0.600000000000 1595268 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": 1115223, "vin": [ { "gen": { "height": 1115213 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f60aad766a198b5c05aa46222a0e4f19e20ebd9e7ba240b97dc0e8764a10ac" } } ], "extra": [ 1, 85, 109, 174, 224, 213, 154, 106, 57, 144, 251, 40, 13, 60, 72, 19, 95, 219, 19, 59, 218, 245, 238, 223, 154, 147, 62, 3, 242, 141, 38, 140, 213, 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