Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17f45ae9e18bace8549db958e142f6b296502e8aa0309c7fcf28ae20445c9c72

Tx prefix hash: e411d8e8078bd2a767052ff914d0d3fb7792c43fa5e6384575947da86a3c48cd
Tx public key: 338d8864099c060fd2f28d7574edbef595606d56e817cdb2e4ec91d149d116dc
Timestamp: 1721394703 Timestamp [UCT]: 2024-07-19 13:11:43 Age [y:d:h:m:s]: 00:252:04:42:01
Block: 1069135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180144 RingCT/type: yes/0
Extra: 01338d8864099c060fd2f28d7574edbef595606d56e817cdb2e4ec91d149d116dc02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2927cd502cb674168422429e5d7c1ef265419706a0430a8fa3d15a467f3b2bb 0.600000000000 1540438 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": 1069145, "vin": [ { "gen": { "height": 1069135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2927cd502cb674168422429e5d7c1ef265419706a0430a8fa3d15a467f3b2bb" } } ], "extra": [ 1, 51, 141, 136, 100, 9, 156, 6, 15, 210, 242, 141, 117, 116, 237, 190, 245, 149, 96, 109, 86, 232, 23, 205, 178, 228, 236, 145, 209, 73, 209, 22, 220, 2, 17, 0, 0, 0, 15, 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