← previous blocknext block →recent activity
Analyzing
Block #87,667,834
15 transactions · 15 stateful · 2026-07-14 08:53:54 UTC
Parallelism
67/100
Blocked
27%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #87,667,834 · 15 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
7w08w19w211w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc36fa358…24cb
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x7071bb5a…522a
0x34b655…2a6f
6 touches
3 conflicts
0xfcb950e3…7273
0x34b655…2a6f
4 touches
1 conflict
0x337f8029…d9cc
0x34b655…2a6f
4 touches
1 conflict
0x588c5b6a…60d2
0x34b655…2a6f
4 touches
1 conflict
0x5b547946…b635
0x34b655…2a6f
4 touches
1 conflict
0x973729b4…d3fb
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 0xc36fa35805…6f24cb
Audit this contract →
← previous block·next block →recent activity