← previous blocknext block →recent activity
Analyzing
Block #106,019,041
15 transactions · 15 stateful · 2026-09-18 23:12:53 UTC
Parallelism
60/100
Blocked
47%
Avg conflicts / tx
1.2
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,019,041 · 15 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
1w03w14w27w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x080d961a…fd1b
0x6f6493…b480
11 touches
15 conflicts
0x1026dc2c…19d3
0x6f6493…b480
11 touches
15 conflicts
0x13345c4a…e6d1
0x6f6493…b480
11 touches
15 conflicts
0x1721c05b…5321
0x6f6493…b480
11 touches
15 conflicts
0x1b57db51…1b1e
0x6f6493…b480
11 touches
15 conflicts
0x207bbde4…8fc6
0x6f6493…b480
11 touches
15 conflicts
0x2ae8baea…0910
0x6f6493…b480
11 touches
15 conflicts
0x3036dd7c…a03d
0x6f6493…b480
11 touches
15 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
15 conflicts on slot 0x080d961a35…28fd1b
Audit this contract →
← previous block·next block →recent activity