← previous blocknext block →recent activity
Analyzing
Block #87,786,133
12 transactions · 11 stateful · 2026-07-14 22:05:30 UTC
Parallelism
83/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,786,133 · 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
1w03w16w07w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xb96a99db…95aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x09cd9841…d332
0x34b655…2a6f
2 touches
0 conflicts
0x0ce02699…904b
0x34b655…2a6f
2 touches
0 conflicts
0x14cfbd32…2d7f
0x34b655…2a6f
2 touches
0 conflicts
0x1595b700…462f
0x34b655…2a6f
2 touches
0 conflicts
0x1e4f2dd7…61eb
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity