← previous blocknext block →recent activity
Analyzing
Block #106,373,023
14 transactions · 13 stateful · 2026-09-20 04:54:25 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.79
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,373,023 · 14 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
1w02w17w08w19w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x156cc811…d4c9
0x6f6493…b480
10 touches
10 conflicts
0x1bc77cc4…5d94
0x6f6493…b480
10 touches
10 conflicts
0x1f458e02…5a36
0x6f6493…b480
10 touches
10 conflicts
0x2b6ab0f7…dcf0
0x6f6493…b480
10 touches
10 conflicts
0x2bbc5c9e…0771
0x6f6493…b480
10 touches
10 conflicts
0x2ec3f5bd…ad23
0x6f6493…b480
10 touches
10 conflicts
0x488a7097…5dd3
0x6f6493…b480
10 touches
10 conflicts
0x69f8c7cb…ad33
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 0x156cc811d7…34d4c9
Audit this contract →
← previous block·next block →recent activity