Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c200d5423e780c2faae507944d35bd78b461c152cee65caa42b633618dc32b2b

Tx prefix hash: 4eab7ec226e7c42c4160b207fc8d20990858d2620fa54338c5089150b1ba70bd
Tx public key: 729fcdb9e5aeaacf09e9f67ed12efc800c9c936a04135aa5c47ee7e47e38d9d1
Timestamp: 1751551319 Timestamp [UCT]: 2025-07-03 14:01:59 Age [y:d:h:m:s]: 00:129:17:29:58
Block: 1317979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90957 RingCT/type: yes/0
Extra: 01729fcdb9e5aeaacf09e9f67ed12efc800c9c936a04135aa5c47ee7e47e38d9d102110000001143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b648ecafdcd4d19d2e27af1d5c62a8419da0f7acf753429c7bdcc10097bb6199 0.600000000000 1805650 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": 1317989, "vin": [ { "gen": { "height": 1317979 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b648ecafdcd4d19d2e27af1d5c62a8419da0f7acf753429c7bdcc10097bb6199" } } ], "extra": [ 1, 114, 159, 205, 185, 229, 174, 170, 207, 9, 233, 246, 126, 209, 46, 252, 128, 12, 156, 147, 106, 4, 19, 90, 165, 196, 126, 231, 228, 126, 56, 217, 209, 2, 17, 0, 0, 0, 17, 67, 132, 109, 102, 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