Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08c34c1b7bd495defc2bbd32b65675521142f60d592e7ba29962840e301935e0

Tx prefix hash: f8bf43230f81833f16c707b49978b17922dc0836ea4783240dc9f772dd721502
Tx public key: cc1b02ff03fa9ec6f1b23d8e806748f7919061355f0f48d86bc3d941f0f3d8cb
Timestamp: 1722282453 Timestamp [UCT]: 2024-07-29 19:47:33 Age [y:d:h:m:s]: 00:247:07:45:06
Block: 1076476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 176653 RingCT/type: yes/0
Extra: 01cc1b02ff03fa9ec6f1b23d8e806748f7919061355f0f48d86bc3d941f0f3d8cb02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d23f27654bb1907c9df47043346eb8d40d373a40b61ecfc144a7bea3dda5e7 0.600000000000 1549013 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": 1076486, "vin": [ { "gen": { "height": 1076476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d23f27654bb1907c9df47043346eb8d40d373a40b61ecfc144a7bea3dda5e7" } } ], "extra": [ 1, 204, 27, 2, 255, 3, 250, 158, 198, 241, 178, 61, 142, 128, 103, 72, 247, 145, 144, 97, 53, 95, 15, 72, 216, 107, 195, 217, 65, 240, 243, 216, 203, 2, 17, 0, 0, 0, 3, 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