← previous blocknext block →recent activity
Analyzing
Block #93,234,767
20 transactions · 19 stateful · 2026-08-05 03:04:05 UTC
Parallelism
75/100
Blocked
37%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,234,767 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w19w210w316w419w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x231ccc13…a7c6
0x34b655…2a6f
10 touches
10 conflicts
0xfed09e59…a493
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x45b3c66c…b788
0x34b655…2a6f
4 touches
1 conflict
0x242fd968…26ed
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x63a8652c…5b43
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 0x231ccc1338…7fa7c6
Audit this contract →
← previous block·next block →recent activity