Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58dfe79ad298238c77bfb1aa58756ec9a4e7509c6547a8f51d1256743e212964

Tx prefix hash: a3ad7e7a6aa274539b5efa41712af7854e5878a05a5186fe9cd7ce1339018181
Tx public key: d8fda995fe4057594accae215a5b36dbeb7aa5927c5ebf6a38011d2a194a7f5b
Timestamp: 1721347997 Timestamp [UCT]: 2024-07-19 00:13:17 Age [y:d:h:m:s]: 00:273:10:06:43
Block: 1068747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195331 RingCT/type: yes/0
Extra: 01d8fda995fe4057594accae215a5b36dbeb7aa5927c5ebf6a38011d2a194a7f5b02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3823b0e2140be9157130de7fdb6a49942c3f67680267db5967b2461bef099ab 0.600000000000 1539896 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": 1068757, "vin": [ { "gen": { "height": 1068747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3823b0e2140be9157130de7fdb6a49942c3f67680267db5967b2461bef099ab" } } ], "extra": [ 1, 216, 253, 169, 149, 254, 64, 87, 89, 74, 204, 174, 33, 90, 91, 54, 219, 235, 122, 165, 146, 124, 94, 191, 106, 56, 1, 29, 42, 25, 74, 127, 91, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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