← previous blocknext block →recent activity
Analyzing
Block #93,445,085
13 transactions · 13 stateful · 2026-08-05 20:41:31 UTC
Parallelism
77/100
Blocked
31%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,445,085 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w08w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
6 touches
3 conflicts
0x8fe37a3f…4c89
0x34b655…2a6f
4 touches
1 conflict
0x720ae293…6a10
0x34b655…2a6f
4 touches
1 conflict
0x7ce5b49a…237c
0x34b655…2a6f
4 touches
1 conflict
0x2ad29b13…92e0
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x4069c511…21c8
0x34b655…2a6f
2 touches
0 conflicts
0x489b8c61…f44c
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity