← previous blocknext block →recent activity
Analyzing
Block #93,510,506
15 transactions · 13 stateful · 2026-08-06 02:10:24 UTC
Parallelism
73/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,510,506 · 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
1w03w16w27w29w010w111w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae9672be…685f
0x34b655…2a6f
8 touches
6 conflicts
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x047e4986…f8de
0x851145…3f07
4 touches
1 conflict
0x1d351a9b…f2dd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xf17636eb…d73c
0x34b655…2a6f
4 touches
1 conflict
0xfaa5c672…5681
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 0xae9672be85…03685f
Audit this contract →
← previous block·next block →recent activity