← previous blocknext block →recent activity
Analyzing
Block #106,282,567
24 transactions · 24 stateful · 2026-09-19 21:19:12 UTC
Parallelism
75/100
Blocked
42%
Avg conflicts / tx
0.83
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,282,567 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w07w112w014w115w216w217w318w419w420w522w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbb571e4…6829
0x34b655…2a6f
8 touches
6 conflicts
0x41bd981d…559d
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0xe098738f…9bbe
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
6 touches
3 conflicts
0x527bf001…9976
0x34b655…2a6f
4 touches
1 conflict
0xbaf6ed88…c179
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
6 conflicts on slot 0xdbb571e456…b26829
Audit this contract →
← previous block·next block →recent activity