← previous blocknext block →recent activity
Analyzing
Block #93,594,532
15 transactions · 12 stateful · 2026-08-06 09:12:47 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,594,532 · 15 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
7w08w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x730f53a0…fff8
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x939cdd56…00c8
0x34b655…2a6f
4 touches
1 conflict
0x5d2e788d…5867
0x34b655…2a6f
4 touches
1 conflict
0x59991669…58c6
0x34b655…2a6f
2 touches
0 conflicts
0x99137b93…c390
0x34b655…2a6f
2 touches
0 conflicts
0x9f3dd8dc…802a
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 0x730f53a001…06fff8
Audit this contract →
← previous block·next block →recent activity