Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ce335eea09a626f8f83d1023995350e76bf096c761a920391598591701e8ea

Tx prefix hash: a768c164ce213d1deb1ba4c578d0008fbddf56b27112a3c7b833205fd3138333
Tx public key: 0a15d909b526144b24b0a7fa292f11c1e05eae450ed68e643d61b09694a7860d
Timestamp: 1764789873 Timestamp [UCT]: 2025-12-03 19:24:33 Age [y:d:h:m:s]: 00:036:00:26:36
Block: 1425770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25785 RingCT/type: yes/0
Extra: 010a15d909b526144b24b0a7fa292f11c1e05eae450ed68e643d61b09694a7860d021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4220203d38b742a426c2c934046b0290c2106cf8e47f937bad2244ae831d55 0.600000000000 1914443 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": 1425780, "vin": [ { "gen": { "height": 1425770 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4220203d38b742a426c2c934046b0290c2106cf8e47f937bad2244ae831d55" } } ], "extra": [ 1, 10, 21, 217, 9, 181, 38, 20, 75, 36, 176, 167, 250, 41, 47, 17, 193, 224, 94, 174, 69, 14, 214, 142, 100, 61, 97, 176, 150, 148, 167, 134, 13, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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