← previous blocknext block →recent activity
Analyzing
Block #86,258,422
19 transactions · 16 stateful · 2026-07-07 19:49:56 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,258,422 · 19 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
1w02w03w19w010w114w115w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa6b89ebb…a66e
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xd93edb3f…94ec
0x34b655…2a6f
6 touches
3 conflicts
0x350e5d8a…601f
0x34b655…2a6f
6 touches
3 conflicts
0xe2a664b0…304f
0x34b655…2a6f
6 touches
3 conflicts
0xfe6395a5…ba6f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
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 0xa6b89ebbaf…5fa66e
Audit this contract →
← previous block·next block →recent activity