← previous blocknext block →recent activity
Analyzing
Block #87,877,208
16 transactions · 9 stateful · 2026-07-15 08:14:38 UTC
Parallelism
88/100
Blocked
11%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,877,208 · 16 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7fa6bb8…32f8
0x34b655…2a6f
4 touches
1 conflict
0x59dccbd8…2bf6
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x266a6b2c…4376
0x34b655…2a6f
2 touches
0 conflicts
0x266a6b2c…4377
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfe038…c16c
0x34b655…2a6f
2 touches
0 conflicts
0x5c79a7db…b7aa
0x34b655…2a6f
2 touches
0 conflicts
0x62d6e82b…a750
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 0xb7fa6bb8f1…d932f8
Audit this contract →
← previous block·next block →recent activity