Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16651af65ac20659c06b6b99c31f6097092b0755eda3eab067cb5e0e86488350

Tx prefix hash: a8ef407440f788ebc380dc77e8be3d2de9c104bf4dc6f13b75e0e6a50479385b
Tx public key: a93e72815b7507e43668e8d2a5b5b7cf0c1a2ff9b5cb102df9b3a6417d87e254
Timestamp: 1710927272 Timestamp [UCT]: 2024-03-20 09:34:32 Age [y:d:h:m:s]: 01:037:00:28:18
Block: 982362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287431 RingCT/type: yes/0
Extra: 01a93e72815b7507e43668e8d2a5b5b7cf0c1a2ff9b5cb102df9b3a6417d87e25402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2cbd0fc53ff72f277717efbf58b4789b9da042a10d291e9d183255392495c46 0.600000000000 1442467 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": 982372, "vin": [ { "gen": { "height": 982362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2cbd0fc53ff72f277717efbf58b4789b9da042a10d291e9d183255392495c46" } } ], "extra": [ 1, 169, 62, 114, 129, 91, 117, 7, 228, 54, 104, 232, 210, 165, 181, 183, 207, 12, 26, 47, 249, 181, 203, 16, 45, 249, 179, 166, 65, 125, 135, 226, 84, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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