← previous blocknext block →recent activity
Analyzing
Block #87,615,368
22 transactions · 17 stateful · 2026-07-14 03:03:15 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,615,368 · 22 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
1w02w03w18w19w210w313w014w116w320w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe197e523…ef9c
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xf2e22c06…42d6
0x34b655…2a6f
6 touches
3 conflicts
0x46361afb…9d6b
0x34b655…2a6f
4 touches
1 conflict
0x5bd818fc…4f86
0x34b655…2a6f
4 touches
1 conflict
0x5d36316b…b0e4
0x34b655…2a6f
4 touches
1 conflict
0x745952b2…d90c
0x34b655…2a6f
4 touches
1 conflict
0x83b16bf0…4083
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 0xe197e52366…87ef9c
Audit this contract →
← previous block·next block →recent activity