← previous blocknext block →recent activity
Analyzing
Block #100,134,501
15 transactions · 15 stateful · 2026-08-29 08:17:30 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,134,501 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe26c4e53…94c3
0x34b655…2a6f
6 touches
3 conflicts
0xc7f6eab9…9e9f
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe26c4e53…94c2
0x34b655…2a6f
6 touches
3 conflicts
0x531db7af…9f89
0x34b655…2a6f
5 touches
3 conflicts
0x81a1e6ee…b9e1
0x8964d7…10f8
4 touches
1 conflict
0x482471ad…122f
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
3 conflicts on slot 0xe26c4e5300…fb94c3
Audit this contract →
← previous block·next block →recent activity