← previous blocknext block →recent activity
Analyzing
Block #106,109,421
19 transactions · 19 stateful · 2026-09-19 06:47:43 UTC
Parallelism
68/100
Blocked
68%
Avg conflicts / tx
1.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,109,421 · 19 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
1w02w13w24w35w28w09w110w211w312w414w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08f9abf1…10bf
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x05cd5432…a826
0x6f6493…b480
10 touches
10 conflicts
0x0de60711…adf2
0x6f6493…b480
10 touches
10 conflicts
0x14c6bfef…8590
0x6f6493…b480
10 touches
10 conflicts
0x193f324a…98f0
0x6f6493…b480
10 touches
10 conflicts
0x1b332906…d550
0x6f6493…b480
10 touches
10 conflicts
0x1ea384b3…4060
0x6f6493…b480
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
10 conflicts on slot 0x08f9abf10a…6910bf
Audit this contract →
← previous block·next block →recent activity