← previous blocknext block →recent activity
Analyzing
Block #93,750,384
18 transactions · 17 stateful · 2026-08-06 22:16:18 UTC
Parallelism
67/100
Blocked
47%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,750,384 · 18 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w18w010w111w212w313w216w417w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfed09e59…a493
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
6 touches
3 conflicts
0x231ccc13…a7c6
0x34b655…2a6f
4 touches
1 conflict
0x43121a72…4b1c
0x34b655…2a6f
4 touches
1 conflict
0x53cccb07…d7f0
0x34b655…2a6f
4 touches
1 conflict
0x682cbce4…1eb0
0x34b655…2a6f
4 touches
1 conflict
0x92115abd…ad76
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 0xfed09e59c7…d6a493
Audit this contract →
← previous block·next block →recent activity