← previous blocknext block →recent activity
Analyzing
Block #93,235,350
24 transactions · 19 stateful · 2026-08-05 03:07:01 UTC
Parallelism
83/100
Blocked
37%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,235,350 · 24 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
1w05w06w17w210w011w012w113w117w119w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0xfd42a6b9…4c81
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x1803586e…d149
0xa6afd3…d132
4 touches
1 conflict
0x1a287886…0266
0xa6afd3…d132
4 touches
1 conflict
0x3464bbc5…a323
0xa6afd3…d132
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
3 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity