Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f5dc524fe9345e0d43cd9f1295fdb4347c8cb0b96e26ada3cfa6f81d88cada4

Tx prefix hash: 1d95f70c93f507a072da0204c22f9445e47614d1f88683838c207bdf3528f496
Tx public key: 0e81196b4c06a2604dce01c2b659c0b70439f72c6ad371d8b73f43e0b51601e7
Timestamp: 1763897988 Timestamp [UCT]: 2025-11-23 11:39:48 Age [y:d:h:m:s]: 00:003:02:37:25
Block: 1418362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2225 RingCT/type: yes/0
Extra: 010e81196b4c06a2604dce01c2b659c0b70439f72c6ad371d8b73f43e0b51601e7021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1376fc9540a683d8ebbbc3ea6205b18d6f2eae17ae912759649563502632013a 0.600000000000 1906893 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": 1418372, "vin": [ { "gen": { "height": 1418362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1376fc9540a683d8ebbbc3ea6205b18d6f2eae17ae912759649563502632013a" } } ], "extra": [ 1, 14, 129, 25, 107, 76, 6, 162, 96, 77, 206, 1, 194, 182, 89, 192, 183, 4, 57, 247, 44, 106, 211, 113, 216, 183, 63, 67, 224, 181, 22, 1, 231, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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