Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07a1fc8bfcc5cc7dae9bc2c81108d792edc8be1e8c9fa62c751616dfccc2540e

Tx prefix hash: b3ad2070baded4816c23f2a45ee3063256a2873dd9d1658af8b7c7fd3859588a
Tx public key: 02bf699039c4960c683c639a24e81048a6779cf62f515d1d5c50e22f065cf4e3
Timestamp: 1763664523 Timestamp [UCT]: 2025-11-20 18:48:43 Age [y:d:h:m:s]: 00:040:18:54:44
Block: 1416426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29208 RingCT/type: yes/0
Extra: 0102bf699039c4960c683c639a24e81048a6779cf62f515d1d5c50e22f065cf4e302110000001570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 075c570dae7d739db9e2c3d9614c4087ffd283580ff2abebce6d727f2f1dfed0 0.600000000000 1904945 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": 1416436, "vin": [ { "gen": { "height": 1416426 } } ], "vout": [ { "amount": 600000000, "target": { "key": "075c570dae7d739db9e2c3d9614c4087ffd283580ff2abebce6d727f2f1dfed0" } } ], "extra": [ 1, 2, 191, 105, 144, 57, 196, 150, 12, 104, 60, 99, 154, 36, 232, 16, 72, 166, 119, 156, 246, 47, 81, 93, 29, 92, 80, 226, 47, 6, 92, 244, 227, 2, 17, 0, 0, 0, 21, 112, 96, 157, 3, 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