← previous blocknext block →recent activity
Analyzing
Block #87,593,930
22 transactions · 18 stateful · 2026-07-14 00:39:53 UTC
Parallelism
77/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,593,930 · 22 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
1w02w14w07w18w29w310w411w114w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7fe05cd…207e
0x34b655…2a6f
8 touches
6 conflicts
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x756ad195…36a3
0x34b655…2a6f
6 touches
3 conflicts
0x18904470…0ef9
0x34b655…2a6f
4 touches
1 conflict
0x26050074…6967
0x34b655…2a6f
4 touches
1 conflict
0x2dfde2ed…8801
0x34b655…2a6f
4 touches
1 conflict
0x53bddbe8…2e5e
0x34b655…2a6f
4 touches
1 conflict
0x7527802e…2ba9
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 0xd7fe05cdfa…d0207e
Audit this contract →
← previous block·next block →recent activity