Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c64ac44b0d5b99ddf1fe96e904d0589c483e596135d1f6537a5464cc04bb8c1

Tx prefix hash: d633483e106b86f0af316fab7d96e0d244acec7fae7573750651360d2f021e7e
Tx public key: 6d80fee0f9ddffb703076a41847692ce0e1d486c44cb7db1e63d67efeae8a4cf
Timestamp: 1700946476 Timestamp [UCT]: 2023-11-25 21:07:56 Age [y:d:h:m:s]: 01:089:19:17:21
Block: 899590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325304 RingCT/type: yes/0
Extra: 016d80fee0f9ddffb703076a41847692ce0e1d486c44cb7db1e63d67efeae8a4cf0211000000014b8f5122000000000000000000

1 output(s) for total of 0.641630317000 dcy

stealth address amount amount idx
00: a7760b823a3eef3e9f8bd98e4e2b8272d3700eab85b71b00cff521b345ccc0f0 0.641630317000 1356049 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": 899600, "vin": [ { "gen": { "height": 899590 } } ], "vout": [ { "amount": 641630317, "target": { "key": "a7760b823a3eef3e9f8bd98e4e2b8272d3700eab85b71b00cff521b345ccc0f0" } } ], "extra": [ 1, 109, 128, 254, 224, 249, 221, 255, 183, 3, 7, 106, 65, 132, 118, 146, 206, 14, 29, 72, 108, 68, 203, 125, 177, 230, 61, 103, 239, 234, 232, 164, 207, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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