← previous blocknext block →recent activity
Analyzing
Block #93,372,933
27 transactions · 23 stateful · 2026-08-05 14:38:45 UTC
Parallelism
85/100
Blocked
48%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,372,933 · 27 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
1w02w13w04w15w06w07w18w29w010w111w112w214w116w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x96529e5c…52c6
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xfecb18c0…01ed
0x34b655…2a6f
6 touches
3 conflicts
0x833f79ee…8fd7
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
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
6 conflicts on slot 0x96529e5ce9…b052c6
Audit this contract →
← previous block·next block →recent activity