Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556462197e0880521d67be3f35137857ca24740f94287a3ff43149ece09e9e5e

Tx prefix hash: c05e488083eafee49d335e6dd49635750788c5e7244addd7fae918b6109d2a85
Tx public key: 0eac9d3285c9dda39d124a6d6be36a1b32ce17b7d0ab7d209dfe3cbebdbf2d5e
Timestamp: 1728644136 Timestamp [UCT]: 2024-10-11 10:55:36 Age [y:d:h:m:s]: 00:181:10:39:42
Block: 1129220 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129465 RingCT/type: yes/0
Extra: 010eac9d3285c9dda39d124a6d6be36a1b32ce17b7d0ab7d209dfe3cbebdbf2d5e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e422a736ecc83a27540ddca93b8bbfad918b02cff65696643cdf2dc2e8bebed 0.600000000000 1612045 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": 1129230, "vin": [ { "gen": { "height": 1129220 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e422a736ecc83a27540ddca93b8bbfad918b02cff65696643cdf2dc2e8bebed" } } ], "extra": [ 1, 14, 172, 157, 50, 133, 201, 221, 163, 157, 18, 74, 109, 107, 227, 106, 27, 50, 206, 23, 183, 208, 171, 125, 32, 157, 254, 60, 190, 189, 191, 45, 94, 2, 17, 0, 0, 0, 1, 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