← previous blocknext block →recent activity
Analyzing
Block #93,671,614
18 transactions · 18 stateful · 2026-08-06 15:40:18 UTC
Parallelism
72/100
Blocked
28%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,671,614 · 18 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
3w04w05w19w210w311w416w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x26040a51…4b8c
0x34b655…2a6f
6 touches
3 conflicts
0x310afe2c…83e1
0x34b655…2a6f
4 touches
1 conflict
0x4bbb6330…f81b
0x34b655…2a6f
4 touches
1 conflict
0x6f97afda…faec
0x34b655…2a6f
4 touches
1 conflict
0x76ed8777…1e5f
0x34b655…2a6f
4 touches
1 conflict
0x7d8b3716…a950
0x34b655…2a6f
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
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 0x26040a511d…974b8c
Audit this contract →
← previous block·next block →recent activity