← previous blocknext block →recent activity
Analyzing
Block #92,161,918
33 transactions · 22 stateful · 2026-08-01 09:05:18 UTC
Parallelism
91/100
Blocked
36%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #92,161,918 · 33 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w112w013w116w117w018w120w022w023w125w126w231w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x34a1ee7e…fb20
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0004
0x63e48b…53f2
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
4 touches
1 conflict
0x9a555477…19a8
0x754704…b603
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x38bcfe5f…6c71
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x34a1ee7e95…7cfb20
Audit this contract →
← previous block·next block →recent activity