← previous blocknext block →recent activity
Analyzing
Block #87,705,456
22 transactions · 16 stateful · 2026-07-14 13:05:37 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,705,456 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w012w114w115w218w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
4 touches
1 conflict
0x2754c3f9…9863
0x34b655…2a6f
4 touches
1 conflict
0x43ad566a…ebd8
0x34b655…2a6f
4 touches
1 conflict
0x6603ed8d…cde2
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
0x34b655…2a6f
4 touches
1 conflict
0x7fd53511…8f76
0x34b655…2a6f
4 touches
1 conflict
0xab5ba139…ea6f
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity