← previous blocknext block →recent activity
Analyzing
Block #93,751,043
13 transactions · 9 stateful · 2026-08-06 22:19:36 UTC
Parallelism
85/100
Blocked
22%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,751,043 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w08w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa36ebe91…7256
0x34b655…2a6f
4 touches
1 conflict
0x6518075e…2b17
0x2a68ba…90c5
4 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0x4e58f1d6…2fca
0x34b655…2a6f
4 touches
1 conflict
0x155e52ca…fac7
0x34b655…2a6f
4 touches
1 conflict
0x58166cc3…9e41
0x40c49f…2af0
3 touches
1 conflict
0x5f5a0edf…ebcc
0x34b655…2a6f
2 touches
0 conflicts
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
1 conflict on slot 0xa36ebe91ad…4f7256
Audit this contract →
← previous block·next block →recent activity