← previous blocknext block →recent activity
Analyzing
Block #93,439,421
30 transactions · 24 stateful · 2026-08-05 20:13:02 UTC
Parallelism
83/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,439,421 · 30 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
1w02w14w08w09w010w011w114w115w216w118w319w220w426w027w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x5d46e6a0…5ed9
0x40c49f…2af0
6 touches
3 conflicts
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002f
0x1b6862…e19c
4 touches
1 conflict
0xb0e4f69d…34e8
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: 0x40c49f17…d22af0
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity