← previous blocknext block →recent activity
Analyzing
Block #93,326,481
11 transactions · 11 stateful · 2026-08-05 10:45:12 UTC
Parallelism
64/100
Blocked
27%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,326,481 · 11 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
5w06w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x8ffa3328…ce11
0xe52b14…7230
6 touches
3 conflicts
0x0bdd5167…7784
0xe52b14…7230
5 touches
3 conflicts
0x1c796c6b…064e
0x34b655…2a6f
2 touches
0 conflicts
0x244fd0dc…ddcc
0x34b655…2a6f
2 touches
0 conflicts
0x3750b746…5a9e
0x34b655…2a6f
2 touches
0 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
2 touches
0 conflicts
0x532a1851…3f74
0x34b655…2a6f
2 touches
0 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: 0xe52b1424…bb7230
6 conflicts on slot 0xf79df061c7…91e005
Audit this contract →
← previous block·next block →recent activity