Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91086f85734d8b169e7f03542a835acb7cc8253de8fc96ac94f8c9af1a586bb0

Tx prefix hash: c3cc0b806cea9ca93e0da079d22c4e7650b51efb723e3a4ad4ed40e475637667
Tx public key: e072c55597133bc815a1e180b072aa89e63da47e2abda31d66e6ba699b8ad2b6
Timestamp: 1714121051 Timestamp [UCT]: 2024-04-26 08:44:11 Age [y:d:h:m:s]: 00:203:02:55:31
Block: 1008815 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145404 RingCT/type: yes/0
Extra: 01e072c55597133bc815a1e180b072aa89e63da47e2abda31d66e6ba699b8ad2b602110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51da04036ed3fcfdc055d978b13dbf298e0a845576813dda2f460530e5b079d3 0.600000000000 1470295 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": 1008825, "vin": [ { "gen": { "height": 1008815 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51da04036ed3fcfdc055d978b13dbf298e0a845576813dda2f460530e5b079d3" } } ], "extra": [ 1, 224, 114, 197, 85, 151, 19, 59, 200, 21, 161, 225, 128, 176, 114, 170, 137, 230, 61, 164, 126, 42, 189, 163, 29, 102, 230, 186, 105, 155, 138, 210, 182, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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