← previous blocknext block →recent activity
Analyzing
Block #92,287,050
22 transactions · 21 stateful · 2026-08-01 19:34:36 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.77
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #92,287,050 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w311w412w513w614w719w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8262a588…40bd
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
8 touches
6 conflicts
0xbde524f4…43bf
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0xe2b888e1…9374
0x34b655…2a6f
5 touches
3 conflicts
0x4bc1abab…5874
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…004c
0x80c745…7210
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 0x8262a588af…b440bd
Audit this contract →
← previous block·next block →recent activity