Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c60cda921e89c181a2869465fbde913491a22aa13ff36677805dcd475abd2861

Tx prefix hash: 5e6ee490b311bb3e263bc6631c703abdad1450d8f7fd0969af3a3ecc7c202709
Tx public key: 204708b501a68679d2b3f269eb86bd4003b29a9f1a2c80c35ad4c4621fb662d5
Timestamp: 1759283313 Timestamp [UCT]: 2025-10-01 01:48:33 Age [y:d:h:m:s]: 00:099:01:44:46
Block: 1380111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70951 RingCT/type: yes/0
Extra: 01204708b501a68679d2b3f269eb86bd4003b29a9f1a2c80c35ad4c4621fb662d5021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 165063af54e210f971357039e51d9c3aad7567adda87c047d5fd67cd4df9325a 0.600000000000 1868222 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": 1380121, "vin": [ { "gen": { "height": 1380111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "165063af54e210f971357039e51d9c3aad7567adda87c047d5fd67cd4df9325a" } } ], "extra": [ 1, 32, 71, 8, 181, 1, 166, 134, 121, 210, 179, 242, 105, 235, 134, 189, 64, 3, 178, 154, 159, 26, 44, 128, 195, 90, 212, 196, 98, 31, 182, 98, 213, 2, 17, 0, 0, 0, 2, 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