← previous blocknext block →recent activity
Analyzing
Block #87,333,145
17 transactions · 17 stateful · 2026-07-12 19:35:04 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,333,145 · 17 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
1w02w07w18w29w110w211w312w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa05444cf…cd70
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x61377ba1…0bef
0xa6afd3…d132
6 touches
3 conflicts
0xad0c145d…72b3
0xa6afd3…d132
6 touches
3 conflicts
0x3d2c514e…49b1
0x34b655…2a6f
4 touches
1 conflict
0x671703d0…94b1
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x793aa64d…b09c
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 0xa05444cff4…1ecd70
Audit this contract →
← previous block·next block →recent activity