← previous blocknext block →recent activity
Analyzing
Block #100,812,843
20 transactions · 18 stateful · 2026-08-31 17:14:34 UTC
Parallelism
80/100
Blocked
56%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #100,812,843 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w39w010w111w012w113w114w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa164d951…1534
0xe1c8b7…3022
8 touches
6 conflicts
0x3b327f76…2b71
0x3bd359…433a
8 touches
6 conflicts
0x44ed742f…63f5
0x3bd359…433a
8 touches
6 conflicts
0x4eb758b8…b13b
0x3bd359…433a
8 touches
6 conflicts
0x00000000…0004
0x49ce4c…2942
8 touches
6 conflicts
0x3b171242…dbb9
0x4d2ea8…7777
8 touches
6 conflicts
0x1ef67ac1…76d0
0xe1c8b7…3022
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0xe1c8b733…e33022
6 conflicts on slot 0xa164d95170…fa1534
Audit this contract →
← previous block·next block →recent activity