Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3022228017607c34325f0174e778866e9f79c7a52a85eb815fcd5efb7c5e2825

Tx prefix hash: f552910651359aa6e0d622a8f843e1ee82090368c477f66217c7409684de4639
Tx public key: ecdac7acd1566dbe9d4bbdbd759dd7be1c8a621f01d66c55d3c0a37ff8980415
Timestamp: 1766150563 Timestamp [UCT]: 2025-12-19 13:22:43 Age [y:d:h:m:s]: 00:045:00:50:10
Block: 1437026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32079 RingCT/type: yes/0
Extra: 01ecdac7acd1566dbe9d4bbdbd759dd7be1c8a621f01d66c55d3c0a37ff8980415021100000005d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 75011d327bf86eca0a3ff0833d0dea58f8e66e5d549d4fe8c82256870cb84e1e 0.600000000000 1925831 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": 1437036, "vin": [ { "gen": { "height": 1437026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "75011d327bf86eca0a3ff0833d0dea58f8e66e5d549d4fe8c82256870cb84e1e" } } ], "extra": [ 1, 236, 218, 199, 172, 209, 86, 109, 190, 157, 75, 189, 189, 117, 157, 215, 190, 28, 138, 98, 31, 1, 214, 108, 85, 211, 192, 163, 127, 248, 152, 4, 21, 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