← previous blocknext block →recent activity
Analyzing
Block #93,359,744
25 transactions · 22 stateful · 2026-08-05 13:32:27 UTC
Parallelism
68/100
Blocked
36%
Avg conflicts / tx
0.84
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #93,359,744 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w310w219w420w521w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5031114…58ac
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xeb0f666f…02d5
0x34b655…2a6f
6 touches
3 conflicts
0x6bdba6fb…4693
0x34b655…2a6f
4 touches
1 conflict
0x6f1bd077…2005
0x34b655…2a6f
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
10 conflicts on slot 0xc503111436…e358ac
Audit this contract →
← previous block·next block →recent activity