← previous blocknext block →recent activity
Analyzing
Block #87,350,810
12 transactions · 10 stateful · 2026-07-12 21:33:08 UTC
Parallelism
83/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,350,810 · 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
3w05w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb2e67228…8a17
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfa4abfe1…582c
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x0e403c18…eac8
0x34b655…2a6f
2 touches
0 conflicts
0x22d41e3b…3336
0x34b655…2a6f
2 touches
0 conflicts
0x263aa68b…6c6a
0x34b655…2a6f
2 touches
0 conflicts
0x41ebf7ed…f662
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 0xb2e67228de…948a17
Audit this contract →
← previous block·next block →recent activity