← previous blocknext block →recent activity
Analyzing
Block #93,407,091
13 transactions · 12 stateful · 2026-08-05 17:30:30 UTC
Parallelism
77/100
Blocked
17%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,407,091 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa279b18d…63bc
0x34b655…2a6f
4 touches
1 conflict
0xc6000ba5…8d65
0x34b655…2a6f
4 touches
1 conflict
0x742870cf…8a43
0x34b655…2a6f
4 touches
1 conflict
0x0ae26137…486a
0x34b655…2a6f
2 touches
0 conflicts
0x0b1cea69…9e3b
0x34b655…2a6f
2 touches
0 conflicts
0x0dba35c5…5b77
0x34b655…2a6f
2 touches
0 conflicts
0x0efc210e…70ab
0x34b655…2a6f
2 touches
0 conflicts
0x387a2497…49e1
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 0xa279b18d93…8363bc
Audit this contract →
← previous block·next block →recent activity