Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db67d2bb4a60ef9f461b8ce4c915e60a0e6ffa0cd2105e3eb710317e9701419b

Tx prefix hash: 554441e3c8cbc179a0a8e15fd7c47c5323afd0bf6354dc28603efe5713d69c78
Tx public key: 3143f0a581a581a8cc307c76794ba9518bccf24173ab1e555d2b0a8843a5d66b
Timestamp: 1751354661 Timestamp [UCT]: 2025-07-01 07:24:21 Age [y:d:h:m:s]: 00:181:21:00:31
Block: 1316384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128247 RingCT/type: yes/0
Extra: 013143f0a581a581a8cc307c76794ba9518bccf24173ab1e555d2b0a8843a5d66b02110000000343846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12b6ff43675f85ee4fda3aee6e42a763429979e148afe0f23b888b0fc825025f 0.600000000000 1804043 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": 1316394, "vin": [ { "gen": { "height": 1316384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12b6ff43675f85ee4fda3aee6e42a763429979e148afe0f23b888b0fc825025f" } } ], "extra": [ 1, 49, 67, 240, 165, 129, 165, 129, 168, 204, 48, 124, 118, 121, 75, 169, 81, 139, 204, 242, 65, 115, 171, 30, 85, 93, 43, 10, 136, 67, 165, 214, 107, 2, 17, 0, 0, 0, 3, 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