Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 438644a8bd66d6fddc783824094366af4635675c3b69899f036bc35d3c10d356

Tx prefix hash: 79992c7e0a7b75def4d7a397321f4dfd25fdd8651a1399728a258e8df7142d18
Tx public key: 8ae65c788badca30b1592705d56c39e45a4d0ac624386a727e4f700d0aa41de2
Timestamp: 1762977783 Timestamp [UCT]: 2025-11-12 20:03:03 Age [y:d:h:m:s]: 00:041:04:03:26
Block: 1410741 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29460 RingCT/type: yes/0
Extra: 018ae65c788badca30b1592705d56c39e45a4d0ac624386a727e4f700d0aa41de2021100000005d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 890027b8f65a0b4128e8fb33d547587e702382f7cefd82ef32b9b8b83bae1220 0.600000000000 1899194 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": 1410751, "vin": [ { "gen": { "height": 1410741 } } ], "vout": [ { "amount": 600000000, "target": { "key": "890027b8f65a0b4128e8fb33d547587e702382f7cefd82ef32b9b8b83bae1220" } } ], "extra": [ 1, 138, 230, 92, 120, 139, 173, 202, 48, 177, 89, 39, 5, 213, 108, 57, 228, 90, 77, 10, 198, 36, 56, 106, 114, 126, 79, 112, 13, 10, 164, 29, 226, 2, 17, 0, 0, 0, 5, 216, 231, 210, 65, 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