Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c5e751c559d0e8ea1d4aa031f80ab5e99b6302892e9a172662765d0874d82a5

Tx prefix hash: 1f692065eead4bb07ed896c4772a0c5d596f53b1475ac7101a51963ed9023a83
Tx public key: afdd2c4812216114557eab8bc24afd3bbd776926281cc00f8ca4cbc1358d47b2
Timestamp: 1694117023 Timestamp [UCT]: 2023-09-07 20:03:43 Age [y:d:h:m:s]: 01:136:04:43:06
Block: 843154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358639 RingCT/type: yes/0
Extra: 01afdd2c4812216114557eab8bc24afd3bbd776926281cc00f8ca4cbc1358d47b202110000000c4b8f5122000000000000000000

1 output(s) for total of 0.986917511000 dcy

stealth address amount amount idx
00: e19a22edd7dd95b72841d6df48fc392f09b2c726b79abffb026ccd5adb44c21c 0.986917511000 1296360 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": 843164, "vin": [ { "gen": { "height": 843154 } } ], "vout": [ { "amount": 986917511, "target": { "key": "e19a22edd7dd95b72841d6df48fc392f09b2c726b79abffb026ccd5adb44c21c" } } ], "extra": [ 1, 175, 221, 44, 72, 18, 33, 97, 20, 85, 126, 171, 139, 194, 74, 253, 59, 189, 119, 105, 38, 40, 28, 192, 15, 140, 164, 203, 193, 53, 141, 71, 178, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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