← previous blocknext block →recent activity
Analyzing
Block #86,688,401
12 transactions · 10 stateful · 2026-07-09 19:45:24 UTC
Parallelism
67/100
Blocked
40%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,688,401 · 12 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
1w02w14w06w18w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x220a8541…6431
0x34b655…2a6f
4 touches
1 conflict
0x073e5fe9…0fb6
0x065c9d…c394
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0003
0x614b85…a284
2 touches
0 conflicts
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 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity