Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d4118b38f4fb1776cffa41a04abd278ff6c74a18c20bd0f4fc5ec6993781459

Tx prefix hash: 5c639cf3ea55a63b3017565554bdbee63ed2484fe0c141f1f59e19bef0bfa628
Tx public key: 0fa692959e469641638f157f6bc3ef1b7605de5a0cee9e80d2b5bbb91c84a892
Timestamp: 1718558445 Timestamp [UCT]: 2024-06-16 17:20:45 Age [y:d:h:m:s]: 00:279:05:27:32
Block: 1045625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199524 RingCT/type: yes/0
Extra: 010fa692959e469641638f157f6bc3ef1b7605de5a0cee9e80d2b5bbb91c84a89202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad796a3d8761cdf5a9a3d1cccb7d6dea8917fd60d1d76fecfa9286e12d9e25a4 0.600000000000 1515244 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": 1045635, "vin": [ { "gen": { "height": 1045625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad796a3d8761cdf5a9a3d1cccb7d6dea8917fd60d1d76fecfa9286e12d9e25a4" } } ], "extra": [ 1, 15, 166, 146, 149, 158, 70, 150, 65, 99, 143, 21, 127, 107, 195, 239, 27, 118, 5, 222, 90, 12, 238, 158, 128, 210, 181, 187, 185, 28, 132, 168, 146, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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