Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c00a4b83842158c80c5031a6268c9815571875de3ed732f94fb79faa04ac0cb

Tx prefix hash: 3b116428e445815ad22f15833d25fe9f74a33270e62b68a8c385e71c46748ac3
Tx public key: 9a0cc1722e62f8ded3bcc1aba3e9df3d616dcc880b6f3a9a7754b00300dd67b8
Timestamp: 1628448771 Timestamp [UCT]: 2021-08-08 18:52:51 Age [y:d:h:m:s]: 03:110:01:57:54
Block: 309909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 851741 RingCT/type: yes/0
Extra: 019a0cc1722e62f8ded3bcc1aba3e9df3d616dcc880b6f3a9a7754b00300dd67b8021100000002a272b9cb000000000000000000

1 output(s) for total of 57.695681770000 dcy

stealth address amount amount idx
00: 338ebf2f93b9acea717c287d4949733c2bd0e7489e1d6d0a7de12f9cb6f7cbff 57.695681770000 645270 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": 309919, "vin": [ { "gen": { "height": 309909 } } ], "vout": [ { "amount": 57695681770, "target": { "key": "338ebf2f93b9acea717c287d4949733c2bd0e7489e1d6d0a7de12f9cb6f7cbff" } } ], "extra": [ 1, 154, 12, 193, 114, 46, 98, 248, 222, 211, 188, 193, 171, 163, 233, 223, 61, 97, 109, 204, 136, 11, 111, 58, 154, 119, 84, 176, 3, 0, 221, 103, 184, 2, 17, 0, 0, 0, 2, 162, 114, 185, 203, 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