← previous blocknext block →recent activity
Analyzing
Block #86,922,231
27 transactions · 23 stateful · 2026-07-10 21:47:59 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
1.19
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,922,231 · 27 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
1w02w14w25w06w17w210w011w112w213w314w416w218w219w321w322w426w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0xa08f40b2…9a93
0x34b655…2a6f
10 touches
10 conflicts
0x6bd6b33e…9557
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x04fdea…47d7
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe718f3c7…c376
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity