← previous blocknext block →recent activity
Analyzing
Block #87,732,961
16 transactions · 16 stateful · 2026-07-14 16:09:48 UTC
Parallelism
69/100
Blocked
31%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,732,961 · 16 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
1w02w14w05w110w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x067c61b8…650f
0x34b655…2a6f
6 touches
3 conflicts
0x46e3da6b…72ca
0x34b655…2a6f
6 touches
3 conflicts
0x1bc07c63…d6ad
0x34b655…2a6f
6 touches
3 conflicts
0x94ba9c4a…41d8
0x34b655…2a6f
6 touches
3 conflicts
0x2877f440…c2c8
0x34b655…2a6f
4 touches
1 conflict
0x3bb680b4…09ef
0x34b655…2a6f
4 touches
1 conflict
0x3cfe4586…0bd9
0x34b655…2a6f
4 touches
1 conflict
0x41d9a134…ccfe
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 0x067c61b803…d7650f
Audit this contract →
← previous block·next block →recent activity