← previous blocknext block →recent activity
Analyzing
Block #93,438,572
20 transactions · 18 stateful · 2026-08-05 20:08:46 UTC
Parallelism
65/100
Blocked
44%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,438,572 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w28w39w410w511w614w116w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x7a2c83a3…a29a
0x34b655…2a6f
8 touches
6 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa942b7a2…7ac0
0x34b655…2a6f
8 touches
6 conflicts
0x3cf50d44…961b
0x34b655…2a6f
6 touches
3 conflicts
0x1e56f6b6…5940
0x34b655…2a6f
6 touches
3 conflicts
0xa33ecf51…7216
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity