Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a59dce4cd3928029fbda43b072f3c251d82dff12c3bff996bf2ba76cd37706af

Tx prefix hash: 225abe5cd97dc17017665210b7412004fa7364b0fec7a490ea8411941d0f405b
Tx public key: 953bdc0d786832095b4c8810949e3c02bcd561b6b34c70b5377b737f86f0c3b0
Timestamp: 1639428585 Timestamp [UCT]: 2021-12-13 20:49:45 Age [y:d:h:m:s]: 03:137:17:57:26
Block: 394855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 877233 RingCT/type: yes/0
Extra: 01953bdc0d786832095b4c8810949e3c02bcd561b6b34c70b5377b737f86f0c3b0021100000001a272b9cb000000000000000000

1 output(s) for total of 30.177400861000 dcy

stealth address amount amount idx
00: af6f2abfbff68615bc41bae52c7771d6eba8dca4cfc3e73ae3872f46eebadc1e 30.177400861000 792582 of 0

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": 394865, "vin": [ { "gen": { "height": 394855 } } ], "vout": [ { "amount": 30177400861, "target": { "key": "af6f2abfbff68615bc41bae52c7771d6eba8dca4cfc3e73ae3872f46eebadc1e" } } ], "extra": [ 1, 149, 59, 220, 13, 120, 104, 50, 9, 91, 76, 136, 16, 148, 158, 60, 2, 188, 213, 97, 182, 179, 76, 112, 181, 55, 123, 115, 127, 134, 240, 195, 176, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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