← previous blocknext block →recent activity
Analyzing
Block #93,505,087
20 transactions · 19 stateful · 2026-08-06 01:43:09 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,505,087 · 20 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
1w02w03w17w18w29w110w211w214w015w116w317w418w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1f79a461…5c8f
0x34b655…2a6f
6 touches
3 conflicts
0xe7ceda84…1a3e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
6 touches
3 conflicts
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0x37bef14c…a6d5
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
0x34b655…2a6f
4 touches
1 conflict
0x528d384f…663d
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
3 conflicts on slot 0x1f79a461c3…455c8f
Audit this contract →
← previous block·next block →recent activity