← previous blocknext block →recent activity
Analyzing
Block #93,440,503
17 transactions · 16 stateful · 2026-08-05 20:18:29 UTC
Parallelism
65/100
Blocked
31%
Avg conflicts / tx
0.76
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,440,503 · 17 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
5w06w19w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd0919e62…a2a8
0x34b655…2a6f
8 touches
6 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xf40e9839…0001
0x34b655…2a6f
5 touches
3 conflicts
0x5c6c0ac8…187f
0x34b655…2a6f
4 touches
1 conflict
0x67209a5a…ab0e
0x34b655…2a6f
4 touches
1 conflict
0x6b47245e…a342
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 0xd0919e626f…7ea2a8
Audit this contract →
← previous block·next block →recent activity