← previous blocknext block →recent activity
Analyzing
Block #93,656,260
22 transactions · 19 stateful · 2026-08-06 14:23:06 UTC
Parallelism
77/100
Blocked
53%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,656,260 · 22 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
2w05w06w17w08w19w110w211w312w213w314w416w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa279b18d…63bc
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xac8a5059…fd42
0x34b655…2a6f
6 touches
3 conflicts
0xb490615a…f5e1
0x34b655…2a6f
6 touches
3 conflicts
0x13649b24…16e8
0x5dd8f3…c69c
4 touches
1 conflict
0x13477596…b14c
0x754704…b603
4 touches
1 conflict
0x69c8bf4a…2ed0
0x754704…b603
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 0xa279b18d93…8363bc
Audit this contract →
← previous block·next block →recent activity