← previous blocknext block →recent activity
Analyzing
Block #87,615,869
7 transactions · 6 stateful · 2026-07-14 03:06:36 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,615,869 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c18dfd3…702b
0x34b655…2a6f
4 touches
1 conflict
0x73ca2093…8dd6
0x34b655…2a6f
4 touches
1 conflict
0x85c3ff67…08a5
0x34b655…2a6f
4 touches
1 conflict
0x85c3ff67…08a6
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0a5d0d7d…c5f2
0x34b655…2a6f
2 touches
0 conflicts
0x0caac81d…a6f7
0x34b655…2a6f
2 touches
0 conflicts
0x117cb8ea…a1dc
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0x6c18dfd397…fc702b
Audit this contract →
← previous block·next block →recent activity