Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b56208909eee5d4b857a3f0384d3195a2e6de10dc270fba5626a03943734251

Tx prefix hash: 2ab689d97e7f09350281556683a041ce81ec05ceb59f0cfc351ca6daa38c98b5
Tx public key: f181b6c50be156c7dbfecda72e93231a4026e46a848911f42344c4109e0cc303
Timestamp: 1641063547 Timestamp [UCT]: 2022-01-01 18:59:07 Age [y:d:h:m:s]: 02:331:14:43:53
Block: 408344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755131 RingCT/type: yes/0
Extra: 01f181b6c50be156c7dbfecda72e93231a4026e46a848911f42344c4109e0cc303021100000001edb0d4a3000000000000000000

1 output(s) for total of 27.226207841000 dcy

stealth address amount amount idx
00: 2b00d2e38fdd6b753eb8342f218a1d833e613edb767a0ca663f16324b234e361 27.226207841000 810341 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": 408354, "vin": [ { "gen": { "height": 408344 } } ], "vout": [ { "amount": 27226207841, "target": { "key": "2b00d2e38fdd6b753eb8342f218a1d833e613edb767a0ca663f16324b234e361" } } ], "extra": [ 1, 241, 129, 182, 197, 11, 225, 86, 199, 219, 254, 205, 167, 46, 147, 35, 26, 64, 38, 228, 106, 132, 137, 17, 244, 35, 68, 196, 16, 158, 12, 195, 3, 2, 17, 0, 0, 0, 1, 237, 176, 212, 163, 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