Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b64d4029fb808c43adc70cbf716c83c6dceae4daad1765647b8bb2ebb1750b8

Tx prefix hash: 16a80a2127a4660a884884611ece60d67afa2381426c279d37a14c4159599213
Tx public key: 2090e81b3c4797dae6f4e09741df2f14eaf5217213fed4aa59963e92795d4a30
Timestamp: 1658140179 Timestamp [UCT]: 2022-07-18 10:29:39 Age [y:d:h:m:s]: 02:208:04:06:03
Block: 546359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 669919 RingCT/type: yes/0
Extra: 012090e81b3c4797dae6f4e09741df2f14eaf5217213fed4aa59963e92795d4a300211000000015eb576c5000000000000000000

1 output(s) for total of 9.499176697000 dcy

stealth address amount amount idx
00: 30a0646be9906a890fda2b37d9b6e05513c4376a5885cb10369faf3439f2fb0e 9.499176697000 977366 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": 546369, "vin": [ { "gen": { "height": 546359 } } ], "vout": [ { "amount": 9499176697, "target": { "key": "30a0646be9906a890fda2b37d9b6e05513c4376a5885cb10369faf3439f2fb0e" } } ], "extra": [ 1, 32, 144, 232, 27, 60, 71, 151, 218, 230, 244, 224, 151, 65, 223, 47, 20, 234, 245, 33, 114, 19, 254, 212, 170, 89, 150, 62, 146, 121, 93, 74, 48, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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