← previous blocknext block →recent activity
Analyzing
Block #106,110,153
17 transactions · 17 stateful · 2026-09-19 06:51:24 UTC
Parallelism
71/100
Blocked
41%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,110,153 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w19w010w111w212w313w414w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d60eaee…c7d8
0x6f6493…b480
10 touches
10 conflicts
0x22e69351…4b87
0x6f6493…b480
10 touches
10 conflicts
0x22ea8331…0060
0x6f6493…b480
10 touches
10 conflicts
0x2351c405…5d2e
0x6f6493…b480
10 touches
10 conflicts
0x4398159b…4eba
0x6f6493…b480
10 touches
10 conflicts
0x4b226aff…1426
0x6f6493…b480
10 touches
10 conflicts
0x4d1e0e6b…e0a2
0x6f6493…b480
10 touches
10 conflicts
0x58829067…aca3
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 0x0d60eaee5b…fec7d8
Audit this contract →
← previous block·next block →recent activity