← previous blocknext block →recent activity
Analyzing
Block #87,265,003
13 transactions · 12 stateful · 2026-07-12 11:59:23 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,265,003 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6e088aaa…3972
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x36a85feb…891b
0x34b655…2a6f
4 touches
1 conflict
0x3d3df40a…28cb
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x818b0b44…ff6f
0x34b655…2a6f
4 touches
1 conflict
0x9cf82fc0…8190
0x34b655…2a6f
4 touches
1 conflict
0xa0bc9ef1…59a0
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
6 conflicts on slot 0x6e088aaa5c…d43972
Audit this contract →
← previous block·next block →recent activity