← previous blocknext block →recent activity
Analyzing
Block #106,053,023
20 transactions · 17 stateful · 2026-09-19 02:03:54 UTC
Parallelism
75/100
Blocked
41%
Avg conflicts / tx
0.7
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,053,023 · 20 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
1w02w13w211w012w113w214w315w417w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e64f1ab…49fa
0x6f6493…b480
9 touches
10 conflicts
0x0eda2d8f…6e31
0x6f6493…b480
9 touches
10 conflicts
0x0edd3d54…cd25
0x6f6493…b480
9 touches
10 conflicts
0x11b2afb9…1cc0
0x6f6493…b480
9 touches
10 conflicts
0x2117618d…4161
0x6f6493…b480
9 touches
10 conflicts
0x2e7b97d5…8d00
0x6f6493…b480
9 touches
10 conflicts
0x385ac44a…2c20
0x6f6493…b480
9 touches
10 conflicts
0x3ded11e0…47fa
0x6f6493…b480
9 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 0x0e64f1abaf…c549fa
Audit this contract →
← previous block·next block →recent activity