← previous blocknext block →recent activity
Analyzing
Block #86,244,877
23 transactions · 19 stateful · 2026-07-07 18:19:22 UTC
Parallelism
83/100
Blocked
47%
Avg conflicts / tx
0.7
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,244,877 · 23 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
3w04w05w18w19w210w011w112w213w317w018w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x1e9a8e72…7138
0x43cf54…7777
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x11560115…bfc2
0x34b655…2a6f
6 touches
3 conflicts
0x3347cbe5…846c
0x34b655…2a6f
4 touches
1 conflict
0x59dbc306…f976
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity