← previous blocknext block →recent activity
Analyzing
Block #92,298,562
19 transactions · 18 stateful · 2026-08-01 20:32:30 UTC
Parallelism
79/100
Blocked
39%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,298,562 · 19 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
3w04w15w28w310w011w112w215w016w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56c55026…fd69
0x34b655…2a6f
8 touches
6 conflicts
0x033cf007…136d
0x34b655…2a6f
6 touches
3 conflicts
0xf3d10975…0d07
0x34b655…2a6f
6 touches
3 conflicts
0x7b42f6a7…f49c
0x34b655…2a6f
6 touches
3 conflicts
0xa1a20fc8…9ac5
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xbde524f4…43bf
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
6 conflicts on slot 0x56c5502653…07fd69
Audit this contract →
← previous block·next block →recent activity