← previous blocknext block →recent activity
Analyzing
Block #106,954,710
30 transactions · 30 stateful · 2026-09-22 05:43:07 UTC
Parallelism
70/100
Blocked
60%
Avg conflicts / tx
1.7
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,954,710 · 30 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
1w02w13w04w16w08w09w110w211w312w414w216w318w119w120w421w522w627w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x337a3739…c710
0x34b655…2a6f
14 touches
21 conflicts
0x01ad5dd0…11a1
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xfcd5e68f…2a12
0x34b655…2a6f
8 touches
6 conflicts
0x4bb4d9a2…62bc
0x34b655…2a6f
8 touches
6 conflicts
0x6c60fbcf…8744
0x34b655…2a6f
8 touches
6 conflicts
0x70986451…c6bd
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
21 conflicts on slot 0x337a37393c…0ac710
Audit this contract →
← previous block·next block →recent activity