Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3c7dd6d9ca66df065f5f591d9435bed9f73dca9969b252b5886026967976e62

Tx prefix hash: cf24edc5b1bfacd7ed46d66dcb54dc0ba461eea85664a4c7de72ceb5e27e2e31
Tx public key: 71494907b1d70e878084c6a21f849564b34893543392776975d0c1d0d2f5b590
Timestamp: 1751392330 Timestamp [UCT]: 2025-07-01 17:52:10 Age [y:d:h:m:s]: 00:129:14:05:30
Block: 1316695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90821 RingCT/type: yes/0
Extra: 0171494907b1d70e878084c6a21f849564b34893543392776975d0c1d0d2f5b590021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68763ee3ec1237f2d0d27e8a8ddf4f3a6a0b0512d9bc1444879e7023458b0afc 0.600000000000 1804358 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": 1316705, "vin": [ { "gen": { "height": 1316695 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68763ee3ec1237f2d0d27e8a8ddf4f3a6a0b0512d9bc1444879e7023458b0afc" } } ], "extra": [ 1, 113, 73, 73, 7, 177, 215, 14, 135, 128, 132, 198, 162, 31, 132, 149, 100, 179, 72, 147, 84, 51, 146, 119, 105, 117, 208, 193, 208, 210, 245, 181, 144, 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