← previous blocknext block →recent activity
Analyzing
Block #87,326,123
15 transactions · 15 stateful · 2026-07-12 18:48:06 UTC
Parallelism
80/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,326,123 · 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
1w02w14w07w08w111w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x2c0bc462…3f0e
0x34b655…2a6f
4 touches
1 conflict
0x3f93d576…f1de
0x34b655…2a6f
4 touches
1 conflict
0x42d169ff…2c03
0x34b655…2a6f
4 touches
1 conflict
0x4814529d…5f07
0x34b655…2a6f
4 touches
1 conflict
0x6f9c6bd9…c66c
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity