← previous blocknext block →recent activity
Analyzing
Block #86,214,740
32 transactions · 28 stateful · 2026-07-07 14:58:05 UTC
Parallelism
84/100
Blocked
39%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,214,740 · 32 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
1w02w13w26w07w08w19w211w112w013w119w322w428w029w130w231w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x5fb273de…1a0c
0xd32edf…ff58
7 touches
6 conflicts
0x2b9c6652…d14e
0x754704…b603
6 touches
3 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x33ab830c…e6db
0x34b655…2a6f
4 touches
1 conflict
0x7e17e82a…9748
0x34b655…2a6f
4 touches
1 conflict
0x917eed5e…6e75
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity