Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24dcc0e80a91a3bdedd4750b86264bf93b40263a10e703268bfddf46544c4849

Tx prefix hash: 430b4f092483f4dfd7aa05b78413adf54333da785d2a9264eac45db6bcddb7dc
Tx public key: bcde6590649ea760d5cca5a431d84ed35bb03824a5b82b8788ffb6db1c5f7b92
Timestamp: 1729686116 Timestamp [UCT]: 2024-10-23 12:21:56 Age [y:d:h:m:s]: 01:017:09:19:10
Block: 1137826 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270810 RingCT/type: yes/0
Extra: 01bcde6590649ea760d5cca5a431d84ed35bb03824a5b82b8788ffb6db1c5f7b920211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14930704e9cf024ba3a6d7ddcf86b479e2d1e8b9e1677c0fa2c4f2b4949fad3c 0.600000000000 1621391 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": 1137836, "vin": [ { "gen": { "height": 1137826 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14930704e9cf024ba3a6d7ddcf86b479e2d1e8b9e1677c0fa2c4f2b4949fad3c" } } ], "extra": [ 1, 188, 222, 101, 144, 100, 158, 167, 96, 213, 204, 165, 164, 49, 216, 78, 211, 91, 176, 56, 36, 165, 184, 43, 135, 136, 255, 182, 219, 28, 95, 123, 146, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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