← previous blocknext block →recent activity
Analyzing
Block #93,521,634
12 transactions · 11 stateful · 2026-08-06 03:06:20 UTC
Parallelism
67/100
Blocked
36%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,521,634 · 12 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
1w02w13w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac8a5059…fd42
0x34b655…2a6f
8 touches
6 conflicts
0x808129fc…f97d
0x34b655…2a6f
4 touches
1 conflict
0x94bb14fe…8f47
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x15dac349…4e37
0x34b655…2a6f
2 touches
0 conflicts
0x23df630a…22a5
0x34b655…2a6f
2 touches
0 conflicts
0x2a2787a1…c9e1
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
6 conflicts on slot 0xac8a5059ab…e9fd42
Audit this contract →
← previous block·next block →recent activity