← previous blocknext block →recent activity
Analyzing
Block #86,138,033
32 transactions · 26 stateful · 2026-07-07 06:26:01 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.66
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,138,033 · 32 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
1w03w14w05w08w09w110w111w016w120w222w323w326w027w128w229w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x95523e2a…4c01
0x065c9d…c394
6 touches
3 conflicts
0x6637e421…af93
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x77ed432f…fa04
0x065c9d…c394
6 touches
3 conflicts
0x29977dde…de04
0xd32edf…ff58
5 touches
3 conflicts
0xb245fe36…d765
0x34b655…2a6f
4 touches
1 conflict
0xd40bddc1…773c
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity