← previous blocknext block →recent activity
Analyzing
Block #93,359,267
32 transactions · 24 stateful · 2026-08-05 13:30:03 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,359,267 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w010w011w113w014w115w217w119w220w323w227w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c5edd82…074a
0x34b655…2a6f
6 touches
3 conflicts
0x6819f434…82c8
0x34b655…2a6f
6 touches
3 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
6 touches
3 conflicts
0xfb874a6c…caa0
0x34b655…2a6f
6 touches
3 conflicts
0xfefb0189…f726
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x3de775b2…319b
0xa6afd3…d132
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
3 conflicts on slot 0x2c5edd828a…a4074a
Audit this contract →
← previous block·next block →recent activity