← previous blocknext block →recent activity
Analyzing
Block #87,259,741
12 transactions · 8 stateful · 2026-07-12 11:24:16 UTC
Parallelism
83/100
Blocked
13%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,259,741 · 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd590db8…613d
0x34b655…2a6f
4 touches
1 conflict
0xc9cbb059…9e23
0x34b655…2a6f
4 touches
1 conflict
0xfd442849…9e43
0x34b655…2a6f
4 touches
1 conflict
0x16c6b563…edf0
0x34b655…2a6f
4 touches
1 conflict
0x4a6982a4…158c
0x34b655…2a6f
4 touches
1 conflict
0x505b37d8…d3fc
0x34b655…2a6f
4 touches
1 conflict
0x6e90b9b1…dca8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
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 0xfd590db8ae…b3613d
Audit this contract →
← previous block·next block →recent activity