← previous blocknext block →recent activity
Analyzing
Block #87,580,869
11 transactions · 11 stateful · 2026-07-13 23:12:33 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.27
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,580,869 · 11 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
5w06w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ee4a6d2…6389
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x99236f7c…65fd
0x34b655…2a6f
4 touches
1 conflict
0x0a49c44b…4b7f
0x34b655…2a6f
2 touches
0 conflicts
0x0b3a6295…1106
0x34b655…2a6f
2 touches
0 conflicts
0x12a92ce8…db54
0x34b655…2a6f
2 touches
0 conflicts
0x1a1df941…41d5
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 0x1ee4a6d212…536389
Audit this contract →
← previous block·next block →recent activity