← previous blocknext block →recent activity
Analyzing
Block #87,443,178
12 transactions · 9 stateful · 2026-07-13 07:50:52 UTC
Parallelism
83/100
Blocked
11%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,443,178 · 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
5w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x320178e8…b5f6
0x34b655…2a6f
4 touches
1 conflict
0xa3d14dff…15d3
0x34b655…2a6f
4 touches
1 conflict
0xa3d14dff…15d4
0x34b655…2a6f
4 touches
1 conflict
0xb3e53c5e…b99c
0x34b655…2a6f
4 touches
1 conflict
0x44063a0c…a912
0x34b655…2a6f
3 touches
1 conflict
0xa65b7ae7…b207
0x34b655…2a6f
3 touches
1 conflict
0x95c47f03…f1bb
0x34b655…2a6f
2 touches
0 conflicts
0x9706392a…02b0
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 0x320178e856…7ab5f6
Audit this contract →
← previous block·next block →recent activity