← previous blocknext block →recent activity
Analyzing
Block #93,502,731
24 transactions · 21 stateful · 2026-08-06 01:31:19 UTC
Parallelism
71/100
Blocked
48%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,502,731 · 24 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w07w18w29w010w111w212w313w415w517w618w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x808129fc…f97d
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0x91855e…ac7e
6 touches
3 conflicts
0x1bbca09e…f873
0x34b655…2a6f
6 touches
3 conflicts
0x5626acdd…8f9d
0x34b655…2a6f
6 touches
3 conflicts
0x861249b9…c98a
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity