Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 328aa968221545e4d33945ce71a59ef6548773e86f309c26d4e18762169e13c0

Tx prefix hash: d51435ff2ee36a34a2dd6d12644bad4243f58cf391865ac3b18b439d281c5bb8
Tx public key: 46e8d4a23a10c510927be74701e57265fbf73d178d7957bae632b4d445ccd4ea
Timestamp: 1575875892 Timestamp [UCT]: 2019-12-09 07:18:12 Age [y:d:h:m:s]: 05:021:13:25:48
Block: 23762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1161485 RingCT/type: yes/0
Extra: 0146e8d4a23a10c510927be74701e57265fbf73d178d7957bae632b4d445ccd4ea02110000000d9159db1e000000000000000000

1 output(s) for total of 511.997100296000 dcy

stealth address amount amount idx
00: 80ac82429c49d9df7fa288c46a530e1a50ecc652f3b9f03f4e12ca3021a1f92a 511.997100296000 38503 of 0

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": 23772, "vin": [ { "gen": { "height": 23762 } } ], "vout": [ { "amount": 511997100296, "target": { "key": "80ac82429c49d9df7fa288c46a530e1a50ecc652f3b9f03f4e12ca3021a1f92a" } } ], "extra": [ 1, 70, 232, 212, 162, 58, 16, 197, 16, 146, 123, 231, 71, 1, 229, 114, 101, 251, 247, 61, 23, 141, 121, 87, 186, 230, 50, 180, 212, 69, 204, 212, 234, 2, 17, 0, 0, 0, 13, 145, 89, 219, 30, 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