← previous blocknext block →recent activity
Analyzing
Block #87,489,940
19 transactions · 17 stateful · 2026-07-13 13:03:34 UTC
Parallelism
74/100
Blocked
35%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,489,940 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w17w18w211w312w413w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x3cb4b659…f735
0x34b655…2a6f
4 touches
1 conflict
0x4c04ce68…d007
0x34b655…2a6f
4 touches
1 conflict
0x5e6fa15e…636d
0x34b655…2a6f
4 touches
1 conflict
0xf79472ee…c820
0x34b655…2a6f
4 touches
1 conflict
0x22f5b72a…22e0
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
6 conflicts on slot 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity