← previous blocknext block →recent activity
Analyzing
Block #108,927,588
55 transactions · 42 stateful · 2026-09-29 03:19:18 UTC
Parallelism
67/100
Blocked
71%
Avg conflicts / tx
2.33
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #108,927,588 · 55 txs across 18 waves · depth 18
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w08w19w316w217w318w419w520w621w722w824w925w1027w1143w344w246w352w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
26 touches
78 conflicts
0xea02471d…1542
0x34b655…2a6f
14 touches
21 conflicts
0x15698ac9…2a46
0x34b655…2a6f
14 touches
21 conflicts
0x271ab0bd…7594
0x34b655…2a6f
10 touches
10 conflicts
0x28aa8ed1…01e5
0x34b655…2a6f
10 touches
10 conflicts
0x3347cbe5…846c
0x34b655…2a6f
10 touches
10 conflicts
0x342fe47d…42ae
0x34b655…2a6f
10 touches
10 conflicts
0x53043411…237a
0x34b655…2a6f
10 touches
10 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
78 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity