Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0d1eee2d4824326bba9713cbc06cf5130a623c12f3241cece2cdaad4e2f09c0

Tx prefix hash: 1eb93a6140c694dd548c0a40da42d9e2acc635a758be7251710756476987d87c
Tx public key: 1d60930bc6fd3825638ac3e3c1c5ac25f0c524c6865e6e6c12c539223c277973
Timestamp: 1702305202 Timestamp [UCT]: 2023-12-11 14:33:22 Age [y:d:h:m:s]: 01:108:17:32:17
Block: 910852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338848 RingCT/type: yes/0
Extra: 011d60930bc6fd3825638ac3e3c1c5ac25f0c524c6865e6e6c12c539223c27797302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e1bc789945ce67934c0165c56f9150b145ba371fea781028959a0a5e570bf3f 0.600000000000 1368027 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": 910862, "vin": [ { "gen": { "height": 910852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e1bc789945ce67934c0165c56f9150b145ba371fea781028959a0a5e570bf3f" } } ], "extra": [ 1, 29, 96, 147, 11, 198, 253, 56, 37, 99, 138, 195, 227, 193, 197, 172, 37, 240, 197, 36, 198, 134, 94, 110, 108, 18, 197, 57, 34, 60, 39, 121, 115, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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