Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b44166f69a109291ad76378516925c598028deaad808f7ff785965181d2502a

Tx prefix hash: ca70d8949e7b577f8c99e2f44a9564737d09f10addc2a9691024b99231e55aac
Tx public key: 1f865af2ee5c309d6c54dcdb311a4e53b910101e8735a3e92e6afa3eee348920
Timestamp: 1764159858 Timestamp [UCT]: 2025-11-26 12:24:18 Age [y:d:h:m:s]: 00:000:20:51:03
Block: 1420534 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 629 RingCT/type: yes/0
Extra: 011f865af2ee5c309d6c54dcdb311a4e53b910101e8735a3e92e6afa3eee348920021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09202dafb2b0d9bcaffcfdb89d1ee73929bc82f4b1d2f2c1e6cec7a09268a586 0.600000000000 1909079 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": 1420544, "vin": [ { "gen": { "height": 1420534 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09202dafb2b0d9bcaffcfdb89d1ee73929bc82f4b1d2f2c1e6cec7a09268a586" } } ], "extra": [ 1, 31, 134, 90, 242, 238, 92, 48, 157, 108, 84, 220, 219, 49, 26, 78, 83, 185, 16, 16, 30, 135, 53, 163, 233, 46, 106, 250, 62, 238, 52, 137, 32, 2, 17, 0, 0, 0, 5, 214, 225, 157, 124, 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