Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be65b66b164f766104180318aed570d841398a9a3d0ce1aee6521158a3d95f9b

Tx prefix hash: 9b9cc5bc6ad1371b010dd15ee7b5cbbc4b3c2b0b58b794684a9ac53988846d69
Tx public key: cc12604df28f7d1b3382ae8b6ab436868cb5d7cfb7a68056a4be4953fa0ffaa1
Timestamp: 1752811725 Timestamp [UCT]: 2025-07-18 04:08:45 Age [y:d:h:m:s]: 00:082:19:47:38
Block: 1327870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57920 RingCT/type: yes/0
Extra: 01cc12604df28f7d1b3382ae8b6ab436868cb5d7cfb7a68056a4be4953fa0ffaa1021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94a1e6539464581afeb3d1042b9a6193062033de47d4c1265090c4a36b054bd9 0.600000000000 1815629 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": 1327880, "vin": [ { "gen": { "height": 1327870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94a1e6539464581afeb3d1042b9a6193062033de47d4c1265090c4a36b054bd9" } } ], "extra": [ 1, 204, 18, 96, 77, 242, 143, 125, 27, 51, 130, 174, 139, 106, 180, 54, 134, 140, 181, 215, 207, 183, 166, 128, 86, 164, 190, 73, 83, 250, 15, 250, 161, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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