← previous blocknext block →recent activity
Analyzing
Block #100,739,898
21 transactions · 16 stateful · 2026-08-31 11:07:25 UTC
Parallelism
67/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,739,898 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w17w18w29w310w416w017w519w120w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbcccf05…6fe5
0x34b655…2a6f
12 touches
15 conflicts
0x53f7214d…8ec6
0x34b655…2a6f
6 touches
3 conflicts
0x9ec251b7…7277
0x34b655…2a6f
6 touches
3 conflicts
0xc87e767e…4bba
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
0x34b655…2a6f
6 touches
3 conflicts
0xba5743c7…21c0
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x0490581d…adaf
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
15 conflicts on slot 0xfbcccf0546…736fe5
Audit this contract →
← previous block·next block →recent activity