Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bdb2400fa65257796a08520ab0936a0d8bee4f1f1071427e0596c21220c60dc

Tx prefix hash: 9f4b7a08e043c7c892b0a6aeca57ae511966166e311d1f2032536fb259d7c69a
Tx public key: eb895a1cfcde2ffffb7ea43b5cfb5e7684134ac564233041eb20da3c5e5f7018
Timestamp: 1634744543 Timestamp [UCT]: 2021-10-20 15:42:23 Age [y:d:h:m:s]: 03:041:18:52:09
Block: 356890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 808033 RingCT/type: yes/0
Extra: 01eb895a1cfcde2ffffb7ea43b5cfb5e7684134ac564233041eb20da3c5e5f701802110000000106faf294000000000000000000

1 output(s) for total of 40.315837999000 dcy

stealth address amount amount idx
00: 47088acddbc39e9934cef1bd41627ae4f2146067d094a9262b43975dd0720218 40.315837999000 727966 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": 356900, "vin": [ { "gen": { "height": 356890 } } ], "vout": [ { "amount": 40315837999, "target": { "key": "47088acddbc39e9934cef1bd41627ae4f2146067d094a9262b43975dd0720218" } } ], "extra": [ 1, 235, 137, 90, 28, 252, 222, 47, 255, 251, 126, 164, 59, 92, 251, 94, 118, 132, 19, 74, 197, 100, 35, 48, 65, 235, 32, 218, 60, 94, 95, 112, 24, 2, 17, 0, 0, 0, 1, 6, 250, 242, 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