← previous blocknext block →recent activity
Analyzing
Block #87,257,113
10 transactions · 8 stateful · 2026-07-12 11:06:41 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,257,113 · 10 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
1w04w15w06w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf094e5be…d695
0x34b655…2a6f
4 touches
1 conflict
0x64852187…6cb0
0x34b655…2a6f
4 touches
1 conflict
0x69b6a6de…86de
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb678410a…0edb
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd526b516…a51a
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
1 conflict on slot 0xf094e5be0e…6ad695
Audit this contract →
← previous block·next block →recent activity