← previous blocknext block →recent activity
Analyzing
Block #93,500,642
11 transactions · 11 stateful · 2026-08-06 01:20:49 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
1.18
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,500,642 · 11 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
2w03w14w25w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6426
0x34b655…2a6f
6 touches
3 conflicts
0xdf071381…d075
0x34b655…2a6f
5 touches
3 conflicts
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0x19e49883…3293
0x851145…3f07
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
10 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity