Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99238265ad943b318d55658dc0ba8dc2be10219f85c9da8c0c03abfe8f8ab432

Tx prefix hash: eac07b13d2a54a79b45d7718a8d277f7bfbe8d6a82058f35e38adbdade99136f
Tx public key: e0c517f52fd0496a4626cae8451038b9e50e0460a028ea1d4b606405eacb3046
Timestamp: 1754422816 Timestamp [UCT]: 2025-08-05 19:40:16 Age [y:d:h:m:s]: 00:063:23:26:31
Block: 1340992 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 44652 RingCT/type: yes/0
Extra: 01e0c517f52fd0496a4626cae8451038b9e50e0460a028ea1d4b606405eacb30460211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82f2246a10c2b3bed089e6c8fa16a3a43a2e65a1a0ad926babf59aa6a01a1aa0 0.600000000000 1828813 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": 1341002, "vin": [ { "gen": { "height": 1340992 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82f2246a10c2b3bed089e6c8fa16a3a43a2e65a1a0ad926babf59aa6a01a1aa0" } } ], "extra": [ 1, 224, 197, 23, 245, 47, 208, 73, 106, 70, 38, 202, 232, 69, 16, 56, 185, 229, 14, 4, 96, 160, 40, 234, 29, 75, 96, 100, 5, 234, 203, 48, 70, 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