← previous blocknext block →recent activity
Analyzing
Block #87,614,599
16 transactions · 15 stateful · 2026-07-14 02:58:07 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,614,599 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w19w010w111w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x41d7e149…baec
0x34b655…2a6f
4 touches
1 conflict
0xb8fa82de…4414
0x34b655…2a6f
4 touches
1 conflict
0x0804b2ba…8a77
0x34b655…2a6f
4 touches
1 conflict
0xfcad4d96…c690
0x34b655…2a6f
4 touches
1 conflict
0xfcad4d96…c691
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity