Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71c6f9405b4cffa8e999da4e848d0567b489f502340393f111f0b465034b55d0

Tx prefix hash: e224e312894a1c8eb2da06a34ea32acd23b4455ace74f2e44bab8809e6919ddf
Tx public key: c93b7b717f3f5eb3f57501fc991206b36211125dc2f8ebc0dde07c0ed6fe0793
Timestamp: 1762207989 Timestamp [UCT]: 2025-11-03 22:13:09 Age [y:d:h:m:s]: 00:016:19:32:39
Block: 1404353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12037 RingCT/type: yes/0
Extra: 01c93b7b717f3f5eb3f57501fc991206b36211125dc2f8ebc0dde07c0ed6fe079302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9800b03c4faa1bd17c8ae6c036e35b8c70a7310a79ab6fa6fd8dd80039f238dd 0.600000000000 1892710 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": 1404363, "vin": [ { "gen": { "height": 1404353 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9800b03c4faa1bd17c8ae6c036e35b8c70a7310a79ab6fa6fd8dd80039f238dd" } } ], "extra": [ 1, 201, 59, 123, 113, 127, 63, 94, 179, 245, 117, 1, 252, 153, 18, 6, 179, 98, 17, 18, 93, 194, 248, 235, 192, 221, 224, 124, 14, 214, 254, 7, 147, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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