Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c12eb5ca71283d6f7fd7a6cdb48abb0276f8fccc162778141f93ea003cce0eb5

Tx prefix hash: 53113d6eecd4c802af8e7f17d8925acb1f42e6676bc4cbf2805c89da5901640f
Tx public key: 84093cda028ea1df71f00fa3d39b3470e129ffe07244242b5f5b8f8cd13c13a2
Timestamp: 1732653239 Timestamp [UCT]: 2024-11-26 20:33:59 Age [y:d:h:m:s]: 00:135:11:01:00
Block: 1162362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96627 RingCT/type: yes/0
Extra: 0184093cda028ea1df71f00fa3d39b3470e129ffe07244242b5f5b8f8cd13c13a2021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9663760023af55dfe389b33baf8d90937d3ed11df0ccfd64ede74498a37170e 0.600000000000 1648017 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": 1162372, "vin": [ { "gen": { "height": 1162362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9663760023af55dfe389b33baf8d90937d3ed11df0ccfd64ede74498a37170e" } } ], "extra": [ 1, 132, 9, 60, 218, 2, 142, 161, 223, 113, 240, 15, 163, 211, 155, 52, 112, 225, 41, 255, 224, 114, 68, 36, 43, 95, 91, 143, 140, 209, 60, 19, 162, 2, 17, 0, 0, 0, 2, 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