← previous blocknext block →recent activity
Analyzing
Block #93,231,691
19 transactions · 14 stateful · 2026-08-05 02:48:37 UTC
Parallelism
74/100
Blocked
50%
Avg conflicts / tx
0.74
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,231,691 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w18w110w212w113w314w218w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0x1803586e…d149
0xa6afd3…d132
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x54998534…d4dd
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x3464bbc5…a323
0xa6afd3…d132
4 touches
1 conflict
0xc824469a…6425
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 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity