← previous blocknext block →recent activity
Analyzing
Block #106,412,631
19 transactions · 19 stateful · 2026-09-20 08:13:44 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,412,631 · 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
2w06w18w09w010w111w212w313w414w516w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x048669d1…1819
0x6f6493…b480
12 touches
15 conflicts
0x15db6d3e…40c1
0x6f6493…b480
12 touches
15 conflicts
0x17eb5f99…c6d1
0x6f6493…b480
12 touches
15 conflicts
0x20c28641…1987
0x6f6493…b480
12 touches
15 conflicts
0x2757ee0d…a146
0x6f6493…b480
12 touches
15 conflicts
0x31adad8b…2ca1
0x6f6493…b480
12 touches
15 conflicts
0x3cfc7d1c…0641
0x6f6493…b480
12 touches
15 conflicts
0x6ca13869…88e9
0x6f6493…b480
12 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 0x048669d1f0…521819
Audit this contract →
← previous block·next block →recent activity