Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dda59109ef07e9d016efc4be91b7908495d625a848a1f4e7f75d8ad9ac77d2b2

Tx prefix hash: 535b17bfe1e5439631ae9623ac9523ac49bff1c3bbf083b4e6ffe7051b3746ab
Tx public key: 8a8f3246a8c5f97f3573f9370907f77d5596e0eb56912f801cdcf7f1ac03036a
Timestamp: 1750220071 Timestamp [UCT]: 2025-06-18 04:14:31 Age [y:d:h:m:s]: 00:198:22:04:08
Block: 1307402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140049 RingCT/type: yes/0
Extra: 018a8f3246a8c5f97f3573f9370907f77d5596e0eb56912f801cdcf7f1ac03036a021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9593de33e425db01a341618e3dddabc1b15a786f0acc58bced4a1b6950f789e 0.600000000000 1795013 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": 1307412, "vin": [ { "gen": { "height": 1307402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9593de33e425db01a341618e3dddabc1b15a786f0acc58bced4a1b6950f789e" } } ], "extra": [ 1, 138, 143, 50, 70, 168, 197, 249, 127, 53, 115, 249, 55, 9, 7, 247, 125, 85, 150, 224, 235, 86, 145, 47, 128, 28, 220, 247, 241, 172, 3, 3, 106, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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