← previous blocknext block →recent activity
Analyzing
Block #86,314,317
39 transactions · 34 stateful · 2026-07-08 02:03:01 UTC
Parallelism
82/100
Blocked
59%
Avg conflicts / tx
1.03
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,314,317 · 39 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w07w08w19w110w211w312w413w014w115w016w120w524w325w627w429w430w133w136w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
6 touches
3 conflicts
0x112cf8ad…6e4f
0xa6afd3…d132
6 touches
3 conflicts
0xc2c6a453…b7ee
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0002
0x04fdea…47d7
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