Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc965fa434b9be42899f59b71323a77997e4ee846c2a1ba51bd05178dc7151ef

Tx prefix hash: 4f24f32358d7ee8bb6ec43f8be7f51148d0bce094896303cdd98d6c1dd7b743a
Tx public key: cb1f8058c7db500a50f0875a4b2cf71edb112d2b91041011bde391dc01bb2d2c
Timestamp: 1730834163 Timestamp [UCT]: 2024-11-05 19:16:03 Age [y:d:h:m:s]: 00:136:14:18:30
Block: 1147287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97458 RingCT/type: yes/0
Extra: 01cb1f8058c7db500a50f0875a4b2cf71edb112d2b91041011bde391dc01bb2d2c021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 65cd01bd32f60f22bf56aa8e6f4196e980f1628104b2d691166936a07f7c156d 0.600000000000 1631982 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": 1147297, "vin": [ { "gen": { "height": 1147287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "65cd01bd32f60f22bf56aa8e6f4196e980f1628104b2d691166936a07f7c156d" } } ], "extra": [ 1, 203, 31, 128, 88, 199, 219, 80, 10, 80, 240, 135, 90, 75, 44, 247, 30, 219, 17, 45, 43, 145, 4, 16, 17, 189, 227, 145, 220, 1, 187, 45, 44, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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