← previous blocknext block →recent activity
Analyzing
Block #87,919,444
29 transactions · 24 stateful · 2026-07-15 12:57:08 UTC
Parallelism
83/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,919,444 · 29 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
6w07w111w012w014w215w320w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x58e16b8d…8dad
0x34b655…2a6f
6 touches
3 conflicts
0x1eec16a0…9e8c
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x49fa14d3…e1e9
0x34b655…2a6f
4 touches
1 conflict
0x57330c5d…9973
0x34b655…2a6f
4 touches
1 conflict
0x5a639697…b266
0x34b655…2a6f
4 touches
1 conflict
0x64aac4d4…ae61
0x34b655…2a6f
4 touches
1 conflict
0x6fe7d366…78ff
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 0x58e16b8dbc…308dad
Audit this contract →
← previous block·next block →recent activity