Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768ce7687a0402b70a4842df44759864e729a1ad3318ef8967942a5827c03ee9

Tx prefix hash: b25c5bfb67b97d079360146eaff839788be9e321e0ab3f54603b632cc2e2bc80
Tx public key: e2f95e10171ec716ac04c3c523ee4cf36d54fc168410b44ba73d3ecccf93d02f
Timestamp: 1634861667 Timestamp [UCT]: 2021-10-22 00:14:27 Age [y:d:h:m:s]: 03:066:04:59:22
Block: 357739 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 825639 RingCT/type: yes/0
Extra: 01e2f95e10171ec716ac04c3c523ee4cf36d54fc168410b44ba73d3ecccf93d02f02110000000737cb3088000000000000000000

1 output(s) for total of 40.055540901000 dcy

stealth address amount amount idx
00: f817a2737c5ed916996314f20bffec5e1cb5afc10c5a4c4e6065319d53267b79 40.055540901000 729331 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": 357749, "vin": [ { "gen": { "height": 357739 } } ], "vout": [ { "amount": 40055540901, "target": { "key": "f817a2737c5ed916996314f20bffec5e1cb5afc10c5a4c4e6065319d53267b79" } } ], "extra": [ 1, 226, 249, 94, 16, 23, 30, 199, 22, 172, 4, 195, 197, 35, 238, 76, 243, 109, 84, 252, 22, 132, 16, 180, 75, 167, 61, 62, 204, 207, 147, 208, 47, 2, 17, 0, 0, 0, 7, 55, 203, 48, 136, 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