← previous blocknext block →recent activity
Analyzing
Block #100,872,371
14 transactions · 14 stateful · 2026-08-31 22:14:13 UTC
Parallelism
57/100
Blocked
36%
Avg conflicts / tx
0.86
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,872,371 · 14 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w19w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x191e0467…70e5
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x8df316ac…c32e
0x34b655…2a6f
4 touches
1 conflict
0x8f267c0d…ebba
0x34b655…2a6f
2 touches
0 conflicts
0xaba6578d…bd48
0x34b655…2a6f
2 touches
0 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
2 touches
0 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: Perpl
10 conflicts on slot 0x191e0467ba…1470e5
Audit this contract →
← previous block·next block →recent activity