← previous blocknext block →recent activity
Analyzing
Block #99,709,368
12 transactions · 10 stateful · 2026-08-27 20:32:15 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #99,709,368 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x57e5abc1…286f
0x34b655…2a6f
4 touches
1 conflict
0x22db2187…cb6b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe01a076a…3472
0x34b655…2a6f
4 touches
1 conflict
0x2867af2c…cb5b
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
2 touches
0 conflicts
0x930d4da0…6eda
0x34b655…2a6f
2 touches
0 conflicts
0x96aa3e9a…62c3
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
1 conflict on slot 0x57e5abc14c…cb286f
Audit this contract →
← previous block·next block →recent activity