Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2df43b315439d7de1027d3714c98b19bb5c4746a28d5a11cb2d3efa369d9aaaf

Tx prefix hash: 91af4003cf6afcce66e8cac6c19d2b31f5bd737d84bf1cd1339aa19f2a66dbdc
Tx public key: d09410fba3be51b9852332d4d792d67c431d318b442d35bff5113246bd3deba9
Timestamp: 1760936654 Timestamp [UCT]: 2025-10-20 05:04:14 Age [y:d:h:m:s]: 00:075:03:40:00
Block: 1393842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 53798 RingCT/type: yes/0
Extra: 01d09410fba3be51b9852332d4d792d67c431d318b442d35bff5113246bd3deba902110000000c25a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea7d0d1d2a0f0f208cce3761dd3b67d2ed81423d08245eea04c0a0d320cd65a0 0.600000000000 1882109 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": 1393852, "vin": [ { "gen": { "height": 1393842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea7d0d1d2a0f0f208cce3761dd3b67d2ed81423d08245eea04c0a0d320cd65a0" } } ], "extra": [ 1, 208, 148, 16, 251, 163, 190, 81, 185, 133, 35, 50, 212, 215, 146, 214, 124, 67, 29, 49, 139, 68, 45, 53, 191, 245, 17, 50, 70, 189, 61, 235, 169, 2, 17, 0, 0, 0, 12, 37, 163, 90, 15, 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