Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 86b8a1c979d6716882303d6b342c7d9cad66c2695e44a364bad7f924639f81a7

Tx prefix hash: 814baf96633a5df71159636ffebb0cffcf74604b89f7dda334ed3ae0adfc5a46
Tx public key: 2861ec1a5183f753959ecc4505c0383323a5374ce83aab619f6177d5e6c161f5
Timestamp: 1636518292 Timestamp [UCT]: 2021-11-10 04:24:52 Age [y:d:h:m:s]: 03:019:10:32:55
Block: 371152 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 792481 RingCT/type: yes/0
Extra: 012861ec1a5183f753959ecc4505c0383323a5374ce83aab619f6177d5e6c161f502110000000242b3953e000000000000000000

1 output(s) for total of 36.160707487000 dcy

stealth address amount amount idx
00: a7a0ae7d777f22ace4d4a7037d9bb64d51efd1c02580f80b10e3d287fae28385 36.160707487000 752182 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": 371162, "vin": [ { "gen": { "height": 371152 } } ], "vout": [ { "amount": 36160707487, "target": { "key": "a7a0ae7d777f22ace4d4a7037d9bb64d51efd1c02580f80b10e3d287fae28385" } } ], "extra": [ 1, 40, 97, 236, 26, 81, 131, 247, 83, 149, 158, 204, 69, 5, 192, 56, 51, 35, 165, 55, 76, 232, 58, 171, 97, 159, 97, 119, 213, 230, 193, 97, 245, 2, 17, 0, 0, 0, 2, 66, 179, 149, 62, 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