Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fc7ba521a3be29366baa43f60a2a56b901de883bfa916595bc76ca688b925a8

Tx prefix hash: df5c03b9ad5128fdc4b0e6b2bc9211bcc77fc276dc05fa44cdbfa6db249fbe7a
Tx public key: a98c2f9f12301e50096bedcd725c589dbc23d27d7e35ec5c98aa10fe94a7a5ed
Timestamp: 1734572295 Timestamp [UCT]: 2024-12-19 01:38:15 Age [y:d:h:m:s]: 00:100:11:44:27
Block: 1178288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71565 RingCT/type: yes/0
Extra: 01a98c2f9f12301e50096bedcd725c589dbc23d27d7e35ec5c98aa10fe94a7a5ed0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be1dfb05239347dc1598690551f47d8115ca7e4e0a608da48e2aaf823d692cf4 0.600000000000 1664675 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": 1178298, "vin": [ { "gen": { "height": 1178288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be1dfb05239347dc1598690551f47d8115ca7e4e0a608da48e2aaf823d692cf4" } } ], "extra": [ 1, 169, 140, 47, 159, 18, 48, 30, 80, 9, 107, 237, 205, 114, 92, 88, 157, 188, 35, 210, 125, 126, 53, 236, 92, 152, 170, 16, 254, 148, 167, 165, 237, 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