← previous blocknext block →recent activity
Analyzing
Block #108,951,895
18 transactions · 17 stateful · 2026-09-29 05:22:04 UTC
Parallelism
72/100
Blocked
35%
Avg conflicts / tx
0.56
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #108,951,895 · 18 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
1w03w04w15w06w17w210w311w412w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9868b52…c77f
0x34b655…2a6f
8 touches
6 conflicts
0x342fe47d…42ae
0x34b655…2a6f
6 touches
3 conflicts
0x3a3c1ed9…9dd5
0x34b655…2a6f
6 touches
3 conflicts
0x48719cbe…5484
0x34b655…2a6f
6 touches
3 conflicts
0x4b52d0b9…2b40
0x34b655…2a6f
6 touches
3 conflicts
0x4ed096a7…1c6c
0x34b655…2a6f
6 touches
3 conflicts
0x631b4113…baa9
0x34b655…2a6f
6 touches
3 conflicts
0x69a58eaa…38a1
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xb9868b5233…c6c77f
Audit this contract →
← previous block·next block →recent activity