← previous blocknext block →recent activity
Analyzing
Block #106,252,830
23 transactions · 22 stateful · 2026-09-19 18:49:34 UTC
Parallelism
61/100
Blocked
59%
Avg conflicts / tx
2.26
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,252,830 · 23 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w18w29w314w115w316w417w518w619w720w821w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba73be23…c570
0x34b655…2a6f
16 touches
28 conflicts
0xa3ed5a09…c6d3
0x34b655…2a6f
12 touches
15 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
12 touches
15 conflicts
0x5717771c…45ed
0x34b655…2a6f
12 touches
15 conflicts
0xf0d81f74…f079
0x34b655…2a6f
10 touches
10 conflicts
0xa27c6ca6…e454
0x34b655…2a6f
8 touches
6 conflicts
0x159cff26…7665
0x34b655…2a6f
8 touches
6 conflicts
0xa6464996…3af9
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
28 conflicts on slot 0xba73be23ce…3fc570
Audit this contract →
← previous block·next block →recent activity