← previous blocknext block →recent activity
Analyzing
Block #108,472,829
25 transactions · 22 stateful · 2026-09-27 13:06:30 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #108,472,829 · 25 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
1w03w14w05w27w08w011w113w214w015w119w020w121w224w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7bd229ad…63b2
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xf5dc501b…831c
0x34b655…2a6f
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x1f5a2e2b…65f1
0x34ae4d…3fc5
4 touches
1 conflict
0x8488f10f…9354
0x34ae4d…3fc5
4 touches
1 conflict
0x8488f10f…9355
0x34ae4d…3fc5
4 touches
1 conflict
0x8488f10f…9356
0x34ae4d…3fc5
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 0x7bd229ade5…6b63b2
Audit this contract →
← previous block·next block →recent activity