← previous blocknext block →recent activity
Analyzing
Block #93,504,017
29 transactions · 27 stateful · 2026-08-06 01:37:47 UTC
Parallelism
86/100
Blocked
48%
Avg conflicts / tx
0.62
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,504,017 · 29 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w17w08w19w010w111w212w213w315w016w218w120w324w125w326w027w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28a16592…3e24
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0x7aae9795…06ed
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
0x34b655…2a6f
4 touches
1 conflict
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
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 0x28a1659289…233e24
Audit this contract →
← previous block·next block →recent activity