Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95af78840e863e515e00efd3d95e13aa1001c83bec2deeadd108e5f9ca5a681f

Tx prefix hash: fb13056d50878c7fa81ecb666fa8767997466144bab994548b55dcc2eaa6eafb
Tx public key: 0348244c4ec5f72f32e47ba5acec8f41328499d3c9432cb1887bf317284ccc48
Timestamp: 1629299753 Timestamp [UCT]: 2021-08-18 15:15:53 Age [y:d:h:m:s]: 03:176:09:03:41
Block: 316509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 899347 RingCT/type: yes/0
Extra: 010348244c4ec5f72f32e47ba5acec8f41328499d3c9432cb1887bf317284ccc4802110000001017696b73000000000000000000

1 output(s) for total of 54.862394684000 dcy

stealth address amount amount idx
00: e8088e1b0f4b26b895eb27ea739a2ef5195d56b776f5c2ac9ecc2ccf29c7a022 54.862394684000 658442 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": 316519, "vin": [ { "gen": { "height": 316509 } } ], "vout": [ { "amount": 54862394684, "target": { "key": "e8088e1b0f4b26b895eb27ea739a2ef5195d56b776f5c2ac9ecc2ccf29c7a022" } } ], "extra": [ 1, 3, 72, 36, 76, 78, 197, 247, 47, 50, 228, 123, 165, 172, 236, 143, 65, 50, 132, 153, 211, 201, 67, 44, 177, 136, 123, 243, 23, 40, 76, 204, 72, 2, 17, 0, 0, 0, 16, 23, 105, 107, 115, 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