Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac85c345b018ed24326a902aa198562d890ba65865e4f948f5d36958d531beb7

Tx prefix hash: 712504563b938ff87ad86c9b13da6c91b6fad8cd70b9c16274175dcae2f39b3e
Tx public key: e8e5e8238efe573ee4964a0c22676da4775bdfd37a71d7e1840c3d216c53c3ce
Timestamp: 1716911281 Timestamp [UCT]: 2024-05-28 15:48:01 Age [y:d:h:m:s]: 00:313:19:37:11
Block: 1031963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224271 RingCT/type: yes/0
Extra: 01e8e5e8238efe573ee4964a0c22676da4775bdfd37a71d7e1840c3d216c53c3ce0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3e1ff146797e671df664b96e67b8352d4a92f1694549ab41698c7e766a2d816 0.600000000000 1500412 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": 1031973, "vin": [ { "gen": { "height": 1031963 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3e1ff146797e671df664b96e67b8352d4a92f1694549ab41698c7e766a2d816" } } ], "extra": [ 1, 232, 229, 232, 35, 142, 254, 87, 62, 228, 150, 74, 12, 34, 103, 109, 164, 119, 91, 223, 211, 122, 113, 215, 225, 132, 12, 61, 33, 108, 83, 195, 206, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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