Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 194eaf2d9454e87b60cd9f48f6a0b126b5c64d1540ebfb6d9cbd6a77a1ec0c1b

Tx prefix hash: 321517213a6967a975b0baf53229caedc303d1e6b843895d08ba3798f5855221
Tx public key: 98fdc22220ea17d6567e96f90ff861ffbedfeaaab9c73e0f34fb8eb746c27b05
Timestamp: 1758278770 Timestamp [UCT]: 2025-09-19 10:46:10 Age [y:d:h:m:s]: 00:094:21:21:41
Block: 1371793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67944 RingCT/type: yes/0
Extra: 0198fdc22220ea17d6567e96f90ff861ffbedfeaaab9c73e0f34fb8eb746c27b05021100000002ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9309b2d7346f4a516b648a32ff6050974dac32a442d2fcbd3188dd209e7f0b44 0.600000000000 1859870 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": 1371803, "vin": [ { "gen": { "height": 1371793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9309b2d7346f4a516b648a32ff6050974dac32a442d2fcbd3188dd209e7f0b44" } } ], "extra": [ 1, 152, 253, 194, 34, 32, 234, 23, 214, 86, 126, 150, 249, 15, 248, 97, 255, 190, 223, 234, 170, 185, 199, 62, 15, 52, 251, 142, 183, 70, 194, 123, 5, 2, 17, 0, 0, 0, 2, 173, 121, 72, 208, 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