Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f137b8e78f7257d317813b967b6ff237b771433db9ab7e5c42c3b38d8bff86a

Tx prefix hash: 6012ecc71e981c46872fd8139d17308a5ce17095da7ac33977f8e72087ff8008
Tx public key: b639f143068e2f473a4918d442a5d04a6f8c1eb6785852cc06e49fdfb81a9652
Timestamp: 1759991270 Timestamp [UCT]: 2025-10-09 06:27:50 Age [y:d:h:m:s]: 00:043:17:37:58
Block: 1385993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31303 RingCT/type: yes/0
Extra: 01b639f143068e2f473a4918d442a5d04a6f8c1eb6785852cc06e49fdfb81a9652021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dec771e4d0f98a0a64568b359111f4e2891a7f33eb4b2f7ea8a05dc3d4615b8b 0.600000000000 1874156 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": 1386003, "vin": [ { "gen": { "height": 1385993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dec771e4d0f98a0a64568b359111f4e2891a7f33eb4b2f7ea8a05dc3d4615b8b" } } ], "extra": [ 1, 182, 57, 241, 67, 6, 142, 47, 71, 58, 73, 24, 212, 66, 165, 208, 74, 111, 140, 30, 182, 120, 88, 82, 204, 6, 228, 159, 223, 184, 26, 150, 82, 2, 17, 0, 0, 0, 1, 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