← previous blocknext block →recent activity
Analyzing
Block #93,440,984
24 transactions · 23 stateful · 2026-08-05 20:20:54 UTC
Parallelism
75/100
Blocked
48%
Avg conflicts / tx
1.08
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,440,984 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w36w07w18w09w111w014w215w316w418w519w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x80656e3b…9240
0x34b655…2a6f
8 touches
6 conflicts
0x5502e1cc…3910
0x34b655…2a6f
6 touches
3 conflicts
0xa95fdd09…a6e8
0x34b655…2a6f
6 touches
3 conflicts
0xaa19f5a3…6248
0x34b655…2a6f
6 touches
3 conflicts
0x8218911e…3bed
0x34b655…2a6f
6 touches
3 conflicts
0xde05a5b2…71be
0xd32edf…ff58
5 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
15 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity