Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9d12bc94359088123c4c16ee2d29a4a6cb11a5bd7f4735cf9fac34759982e61

Tx prefix hash: 1fdf92e7de039f495af8311df29d1156b354a6cbe759f3e06fc71362acec619e
Tx public key: 66ae5a41536e1a020b0369855db32ad12c91a6d9d9ac11a323eee952f396079d
Timestamp: 1754415570 Timestamp [UCT]: 2025-08-05 17:39:30 Age [y:d:h:m:s]: 00:108:00:47:10
Block: 1340930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 76198 RingCT/type: yes/0
Extra: 0166ae5a41536e1a020b0369855db32ad12c91a6d9d9ac11a323eee952f396079d0211000000028368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4828ee020988a0552ce5b8fe79b6f5165f49adfc78307e1ec5302d2e35a92d84 0.600000000000 1828751 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": 1340940, "vin": [ { "gen": { "height": 1340930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4828ee020988a0552ce5b8fe79b6f5165f49adfc78307e1ec5302d2e35a92d84" } } ], "extra": [ 1, 102, 174, 90, 65, 83, 110, 26, 2, 11, 3, 105, 133, 93, 179, 42, 209, 44, 145, 166, 217, 217, 172, 17, 163, 35, 238, 233, 82, 243, 150, 7, 157, 2, 17, 0, 0, 0, 2, 131, 104, 38, 109, 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