← previous blocknext block →recent activity
Analyzing
Block #93,359,872
32 transactions · 27 stateful · 2026-08-05 13:33:05 UTC
Parallelism
81/100
Blocked
44%
Avg conflicts / tx
0.66
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,359,872 · 32 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
1w02w13w04w15w29w010w111w214w015w116w218w320w221w327w428w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5031114…58ac
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x55a37e65…9d36
0x34b655…2a6f
4 touches
1 conflict
0x68a39b75…747d
0x34b655…2a6f
4 touches
1 conflict
0xbbeac3b7…c14b
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
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 0xc503111436…e358ac
Audit this contract →
← previous block·next block →recent activity