← previous blocknext block →recent activity
Analyzing
Block #106,301,570
23 transactions · 23 stateful · 2026-09-19 22:54:50 UTC
Parallelism
57/100
Blocked
70%
Avg conflicts / tx
2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,301,570 · 23 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w16w48w59w611w712w820w921w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe1cf03a5…64c6
0x6f6493…b480
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xca9f6da9…5e70
0x6f6493…b480
10 touches
10 conflicts
0xce8c623e…358e
0x6f6493…b480
10 touches
10 conflicts
0xdb0849c9…2d6f
0x6f6493…b480
10 touches
10 conflicts
0x837fb53e…b580
0x34b655…2a6f
10 touches
10 conflicts
0x230f558f…2283
0x6f6493…b480
10 touches
10 conflicts
0x230f558f…2287
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: 0x6f6493e3…08b480
10 conflicts on slot 0xe1cf03a50a…5464c6
Audit this contract →
← previous block·next block →recent activity