← previous blocknext block →recent activity
Analyzing
Block #93,667,412
21 transactions · 18 stateful · 2026-08-06 15:19:10 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,667,412 · 21 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
3w04w15w06w17w28w09w211w012w115w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f5a0edf…ebcc
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0bfb4aa3…2132
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0x24ca1902…7a87
0x34b655…2a6f
4 touches
1 conflict
0x65ca7c8d…6df7
0x34b655…2a6f
4 touches
1 conflict
0x66cc2a1f…564d
0x34b655…2a6f
4 touches
1 conflict
0x6e9c9774…b56c
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
3 conflicts on slot 0x5f5a0edfcc…1eebcc
Audit this contract →
← previous block·next block →recent activity