Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fe92e0919da53d7e8b5fa30994b3723a27144f660afd36a2f73ae5a254ba211

Tx prefix hash: c4dfb011ad0f57569324bf704c65ca26a81c53ae8b658e72563a2034f92cb6d2
Tx public key: 09fe2266056a136ce9b89f323084801959641ec4c4a3e4ef520e577a8b8a3fd1
Timestamp: 1759190371 Timestamp [UCT]: 2025-09-29 23:59:31 Age [y:d:h:m:s]: 00:122:04:21:52
Block: 1379339 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 87313 RingCT/type: yes/0
Extra: 0109fe2266056a136ce9b89f323084801959641ec4c4a3e4ef520e577a8b8a3fd1021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 441fc07a13b16bb1396a45a28ea3ce4d8f8e0a85e731732ffc074cabab70278c 0.600000000000 1867436 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": 1379349, "vin": [ { "gen": { "height": 1379339 } } ], "vout": [ { "amount": 600000000, "target": { "key": "441fc07a13b16bb1396a45a28ea3ce4d8f8e0a85e731732ffc074cabab70278c" } } ], "extra": [ 1, 9, 254, 34, 102, 5, 106, 19, 108, 233, 184, 159, 50, 48, 132, 128, 25, 89, 100, 30, 196, 196, 163, 228, 239, 82, 14, 87, 122, 139, 138, 63, 209, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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