← previous blocknext block →recent activity
Analyzing
Block #92,331,494
14 transactions · 13 stateful · 2026-08-01 23:18:07 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,331,494 · 14 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
2w03w14w25w06w17w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4f65e04…6928
0x34b655…2a6f
8 touches
6 conflicts
0xfa08dba9…81d9
0x7b9256…1fb2
6 touches
3 conflicts
0x177211e2…1c2d
0x754704…b603
6 touches
3 conflicts
0xe1f61186…e2f8
0x754704…b603
6 touches
3 conflicts
0x00000000…0006
0x7b9256…1fb2
6 touches
3 conflicts
0x317315f4…a231
0x7b9256…1fb2
6 touches
3 conflicts
0x317315f4…a232
0x7b9256…1fb2
6 touches
3 conflicts
0xfa08dba9…81d5
0x7b9256…1fb2
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
6 conflicts on slot 0xe4f65e04a3…ce6928
Audit this contract →
← previous block·next block →recent activity