← previous blocknext block →recent activity
Analyzing
Block #86,335,318
19 transactions · 18 stateful · 2026-07-08 04:23:17 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #86,335,318 · 19 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
2w03w16w211w314w415w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8a5ced1c…3b29
0x34b655…2a6f
8 touches
6 conflicts
0x65a3b3b0…ad2d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xddd20e39…d524
0x34b655…2a6f
6 touches
3 conflicts
0x96dd83e6…a507
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x98a94f33…b1b5
0x34b655…2a6f
4 touches
1 conflict
0xb577a4a7…a670
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
6 conflicts on slot 0x8a5ced1cae…443b29
Audit this contract →
← previous block·next block →recent activity