← previous blocknext block →recent activity
Analyzing
Block #93,407,717
11 transactions · 10 stateful · 2026-08-05 17:33:39 UTC
Parallelism
55/100
Blocked
40%
Avg conflicts / tx
0.64
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,407,717 · 11 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
1w02w14w25w36w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66d5e476…8a1f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x4e50038e…6e29
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x84e3ed5a…1678
0x34b655…2a6f
6 touches
3 conflicts
0xb0651d04…fb27
0x34b655…2a6f
5 touches
3 conflicts
0x5767b983…3310
0x34b655…2a6f
5 touches
3 conflicts
0xc824469a…641d
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
3 conflicts on slot 0x66d5e476c0…268a1f
Audit this contract →
← previous block·next block →recent activity