← previous blocknext block →recent activity
Analyzing
Block #87,622,102
17 transactions · 14 stateful · 2026-07-14 03:48:15 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,622,102 · 17 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
2w04w15w29w310w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf9516d52…5364
0x34b655…2a6f
4 touches
1 conflict
0xe7a04bd8…289b
0x34b655…2a6f
4 touches
1 conflict
0xf2f4727d…cdb7
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0xf9516d52…5363
0x34b655…2a6f
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x1b5d2e60…99b5
0x34b655…2a6f
4 touches
1 conflict
0x55eef346…d185
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 0xf9516d52ba…415364
Audit this contract →
← previous block·next block →recent activity