Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e22314e7e80b7cebf017714ecb0603b8c94247a81414e45649e7bdc7eb2a5107

Tx prefix hash: 898c93b74b3fd98b861e6ef40d613ba629a9809d0b905c77b0a09401f0a9f5e2
Tx public key: bc5944e7b5233b4ef1c3c8a4ccb6091690755906246a2bc218477a4a0cb0e36c
Timestamp: 1763473388 Timestamp [UCT]: 2025-11-18 13:43:08 Age [y:d:h:m:s]: 00:009:19:47:38
Block: 1414847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7036 RingCT/type: yes/0
Extra: 01bc5944e7b5233b4ef1c3c8a4ccb6091690755906246a2bc218477a4a0cb0e36c021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9548d4cadf8c8745fe1b3d4b59b2081dd6d1e7eb34106f5e2a0a599877ff062b 0.600000000000 1903340 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": 1414857, "vin": [ { "gen": { "height": 1414847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9548d4cadf8c8745fe1b3d4b59b2081dd6d1e7eb34106f5e2a0a599877ff062b" } } ], "extra": [ 1, 188, 89, 68, 231, 181, 35, 59, 78, 241, 195, 200, 164, 204, 182, 9, 22, 144, 117, 89, 6, 36, 106, 43, 194, 24, 71, 122, 74, 12, 176, 227, 108, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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