Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa55d741dbc3258a3da849a9de8741f4afbfae3062150e1bf73d6f3a2848d827

Tx prefix hash: b0c3a770693e51c6f93f0f5b78afa7fce7d3b52e0217bd0820b5ec0628a11f26
Tx public key: 096a63031fbd68c2f6c4dba9f76f3e5ce24f46f55d0761d1f419313b6a0e120c
Timestamp: 1765222895 Timestamp [UCT]: 2025-12-08 19:41:35 Age [y:d:h:m:s]: 00:025:12:02:16
Block: 1429343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 18268 RingCT/type: yes/0
Extra: 01096a63031fbd68c2f6c4dba9f76f3e5ce24f46f55d0761d1f419313b6a0e120c020900000014d48050ef00

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f9de840a86f0fd995a9a123e726c1734cd12d98369e4aa0940b02707d2f1e5e6 0.600000000000 1918068 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": 1429353, "vin": [ { "gen": { "height": 1429343 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f9de840a86f0fd995a9a123e726c1734cd12d98369e4aa0940b02707d2f1e5e6" } } ], "extra": [ 1, 9, 106, 99, 3, 31, 189, 104, 194, 246, 196, 219, 169, 247, 111, 62, 92, 226, 79, 70, 245, 93, 7, 97, 209, 244, 25, 49, 59, 106, 14, 18, 12, 2, 9, 0, 0, 0, 20, 212, 128, 80, 239, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8