← previous blocknext block →recent activity
Analyzing
Block #106,003,614
16 transactions · 16 stateful · 2026-09-18 21:55:15 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.75
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,003,614 · 16 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
1w02w19w010w111w012w113w214w315w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03bb2aaf…7d5c
0x6f6493…b480
10 touches
10 conflicts
0x07e399a7…2544
0x6f6493…b480
10 touches
10 conflicts
0x0f6e4786…a866
0x6f6493…b480
10 touches
10 conflicts
0x22522a33…ba61
0x6f6493…b480
10 touches
10 conflicts
0x278a2067…1205
0x6f6493…b480
10 touches
10 conflicts
0x496ff9a8…d870
0x6f6493…b480
10 touches
10 conflicts
0x4ad2fac7…9d63
0x6f6493…b480
10 touches
10 conflicts
0x572d9927…5a8f
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 0x03bb2aafa2…767d5c
Audit this contract →
← previous block·next block →recent activity