Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 765659a430204249e489851e65ce81eb14b43b5c9906b11365e2e4132df0d8d4

Tx prefix hash: cd66f9b8694cbb65e2275a4ea0a0ea627f94ac6a4c0cf8fd81e2be0a840c4ca0
Tx public key: 290284cb9da5c68dea03f5e43debb722a4fc92504d0f29456078013f65cec063
Timestamp: 1764358658 Timestamp [UCT]: 2025-11-28 19:37:38 Age [y:d:h:m:s]: 00:000:02:03:52
Block: 1422187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56 RingCT/type: yes/0
Extra: 01290284cb9da5c68dea03f5e43debb722a4fc92504d0f29456078013f65cec06302110000000134af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e80f9989db5bc2b27de7a008d4797421bb4a7cb28f5add18f28f22fdb4249eb 0.600000000000 1910752 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": 1422197, "vin": [ { "gen": { "height": 1422187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e80f9989db5bc2b27de7a008d4797421bb4a7cb28f5add18f28f22fdb4249eb" } } ], "extra": [ 1, 41, 2, 132, 203, 157, 165, 198, 141, 234, 3, 245, 228, 61, 235, 183, 34, 164, 252, 146, 80, 77, 15, 41, 69, 96, 120, 1, 63, 101, 206, 192, 99, 2, 17, 0, 0, 0, 1, 52, 175, 49, 204, 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