← previous blocknext block →recent activity
Analyzing
Block #86,456,136
21 transactions · 20 stateful · 2026-07-08 17:50:27 UTC
Parallelism
76/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,456,136 · 21 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
1w02w03w14w05w16w27w38w418w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x0b2bec5d…6e4a
0x34b655…2a6f
8 touches
6 conflicts
0xa0efa7bc…8b24
0x34b655…2a6f
8 touches
6 conflicts
0xaa48195d…ffee
0x34b655…2a6f
8 touches
6 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
8 touches
6 conflicts
0xd3ef5630…0de9
0x34b655…2a6f
8 touches
6 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity