← previous blocknext block →recent activity
Analyzing
Block #93,358,228
19 transactions · 17 stateful · 2026-08-05 13:24:49 UTC
Parallelism
68/100
Blocked
53%
Avg conflicts / tx
1.32
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,358,228 · 19 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
1w02w13w04w15w26w38w210w311w414w515w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6939e474…4256
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x74362807…e577
0x34b655…2a6f
8 touches
6 conflicts
0x18eedf0c…0da7
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x6939e474b1…154256
Audit this contract →
← previous block·next block →recent activity