← previous blocknext block →recent activity
Analyzing
Block #87,758,418
16 transactions · 14 stateful · 2026-07-14 19:00:03 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,758,418 · 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
2w03w110w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b9ea90e…c0f5
0x34b655…2a6f
4 touches
1 conflict
0x1d521b7f…b009
0x34b655…2a6f
4 touches
1 conflict
0x20ff72d4…5971
0x34b655…2a6f
4 touches
1 conflict
0x264f7d7d…8444
0x34b655…2a6f
4 touches
1 conflict
0x2bec5ebb…ab7d
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x3e0c8fff…34c8
0x34b655…2a6f
4 touches
1 conflict
0x3fde350e…8d43
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 0x1b9ea90ebb…53c0f5
Audit this contract →
← previous block·next block →recent activity