Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 637fe2b3599549ea266947408003c9d0d66948c3840c6b971f51dc379bd8ea51

Tx prefix hash: 1f173c060f1a8aa572d9584902d8547ac4ce7c7f5109f2652bade30ad868ff0c
Tx public key: c048c161733f1db852a16850e0ffeab7a5459a2bf6963a3484f256ec5f6b82b2
Timestamp: 1764650481 Timestamp [UCT]: 2025-12-02 04:41:21 Age [y:d:h:m:s]: 00:037:15:09:48
Block: 1424593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 26962 RingCT/type: yes/0
Extra: 01c048c161733f1db852a16850e0ffeab7a5459a2bf6963a3484f256ec5f6b82b2021100000009d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 539ef96fb5962b2d9f8e50d0d90c6594ae0a6bfa674561e989e23ee23ba1f23a 0.600000000000 1913224 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": 1424603, "vin": [ { "gen": { "height": 1424593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "539ef96fb5962b2d9f8e50d0d90c6594ae0a6bfa674561e989e23ee23ba1f23a" } } ], "extra": [ 1, 192, 72, 193, 97, 115, 63, 29, 184, 82, 161, 104, 80, 224, 255, 234, 183, 165, 69, 154, 43, 246, 150, 58, 52, 132, 242, 86, 236, 95, 107, 130, 178, 2, 17, 0, 0, 0, 9, 214, 225, 157, 124, 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