← previous blocknext block →recent activity
Analyzing
Block #108,951,896
24 transactions · 19 stateful · 2026-09-29 05:22:04 UTC
Parallelism
83/100
Blocked
53%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #108,951,896 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w27w08w19w210w312w013w114w215w316w317w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x342fe47d…42ae
0x34b655…2a6f
8 touches
6 conflicts
0x3a3c1ed9…9dd5
0x34b655…2a6f
8 touches
6 conflicts
0x48719cbe…5484
0x34b655…2a6f
8 touches
6 conflicts
0x631b4113…baa9
0x34b655…2a6f
8 touches
6 conflicts
0x69a58eaa…38a1
0x34b655…2a6f
8 touches
6 conflicts
0x6b583dde…23c7
0x34b655…2a6f
8 touches
6 conflicts
0x751f0341…fe9b
0x34b655…2a6f
8 touches
6 conflicts
0x99080043…b90f
0x34b655…2a6f
8 touches
6 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 0x342fe47d2f…2642ae
Audit this contract →
← previous block·next block →recent activity