← previous blocknext block →recent activity
Analyzing
Block #93,456,285
15 transactions · 13 stateful · 2026-08-05 21:37:49 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,456,285 · 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
3w04w16w09w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb56b94f6…a7f1
0x34b655…2a6f
8 touches
6 conflicts
0x428b6e5b…8909
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x50c0dd87…1128
0x34b655…2a6f
6 touches
3 conflicts
0x8eb21bd9…aa8b
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xf6884b1c…8b7f
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 0xb56b94f64b…29a7f1
Audit this contract →
← previous block·next block →recent activity