← previous blocknext block →recent activity
Analyzing
Block #86,628,090
25 transactions · 23 stateful · 2026-07-09 13:01:19 UTC
Parallelism
84/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,628,090 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w15w06w18w19w011w015w120w121w222w323w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x076e4b80…4d01
0x34b655…2a6f
4 touches
1 conflict
0x140eb1ca…bc07
0x34b655…2a6f
4 touches
1 conflict
0x1cbd009b…629b
0x34b655…2a6f
4 touches
1 conflict
0x1e334ac0…11d3
0x34b655…2a6f
4 touches
1 conflict
0x22f55465…3968
0x34b655…2a6f
4 touches
1 conflict
0x25191452…d2ed
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
3 conflicts on slot 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity