Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c94c195fb620fdded37149cf9654e4ec0d9ec6a84d1bbf04747e76cbea415993

Tx prefix hash: f1bec45b169a6a4549e13a6fd328ba96307841f4404979c270fd73df12affd21
Tx public key: a003fd7800fbb79b9bb9bf5f1c9d75470f53b88208e8bca538ea92a1e7fffa94
Timestamp: 1747354653 Timestamp [UCT]: 2025-05-16 00:17:33 Age [y:d:h:m:s]: 00:145:01:12:44
Block: 1283795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101322 RingCT/type: yes/0
Extra: 01a003fd7800fbb79b9bb9bf5f1c9d75470f53b88208e8bca538ea92a1e7fffa940211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f7b2b6f79162eba4ef3254b8a21a5409109be7245d73f4757ee398d14fb80ca 0.600000000000 1771214 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": 1283805, "vin": [ { "gen": { "height": 1283795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f7b2b6f79162eba4ef3254b8a21a5409109be7245d73f4757ee398d14fb80ca" } } ], "extra": [ 1, 160, 3, 253, 120, 0, 251, 183, 155, 155, 185, 191, 95, 28, 157, 117, 71, 15, 83, 184, 130, 8, 232, 188, 165, 56, 234, 146, 161, 231, 255, 250, 148, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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