← previous blocknext block →recent activity
Analyzing
Block #86,616,818
23 transactions · 21 stateful · 2026-07-09 11:46:05 UTC
Parallelism
74/100
Blocked
38%
Avg conflicts / tx
0.57
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,616,818 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w37w18w010w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x1e4019d7…ad89
0x34b655…2a6f
4 touches
1 conflict
0x2b0a93aa…499f
0x34b655…2a6f
4 touches
1 conflict
0x3d2c514e…49b1
0x34b655…2a6f
4 touches
1 conflict
0x4f17dc85…c493
0x34b655…2a6f
4 touches
1 conflict
0x5b2af826…16c8
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity