← previous blocknext block →recent activity
Analyzing
Block #93,402,224
23 transactions · 21 stateful · 2026-08-05 17:06:02 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.83
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,402,224 · 23 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
4w08w19w210w311w412w313w414w518w621w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x43fd3667…094b
0x34b655…2a6f
8 touches
6 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x749a4cb2…15f8
0x34b655…2a6f
6 touches
3 conflicts
0x6659466a…5090
0x34b655…2a6f
4 touches
1 conflict
0x6bf3c40e…4f8a
0x34b655…2a6f
4 touches
1 conflict
0x74b9ea61…c21c
0x34b655…2a6f
4 touches
1 conflict
0x7f9061c2…46d8
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
6 conflicts on slot 0x43fd366775…d0094b
Audit this contract →
← previous block·next block →recent activity