← previous blocknext block →recent activity
Analyzing
Block #87,594,819
25 transactions · 18 stateful · 2026-07-14 00:45:50 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
0.68
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #87,594,819 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w113w014w215w316w418w519w620w723w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6fe7d366…78ff
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0x3f85f288…7c97
0x34b655…2a6f
4 touches
1 conflict
0x469e824a…d814
0x34b655…2a6f
4 touches
1 conflict
0x46fdb575…fe2d
0x34b655…2a6f
4 touches
1 conflict
0x4b628349…f327
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x60c6a924…94de
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 0x6fe7d366be…a578ff
Audit this contract →
← previous block·next block →recent activity