← previous blocknext block →recent activity
Analyzing
Block #106,276,159
20 transactions · 19 stateful · 2026-09-19 20:46:58 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,276,159 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w19w010w111w012w113w214w316w219w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x16e8a2fe…0a38
0x6f6493…b480
8 touches
6 conflicts
0x20156eac…4023
0x6f6493…b480
8 touches
6 conflicts
0x3fff3652…d2eb
0x6f6493…b480
8 touches
6 conflicts
0x41a2880b…8258
0x6f6493…b480
8 touches
6 conflicts
0x41a2880b…825c
0x6f6493…b480
8 touches
6 conflicts
0x444615a9…34db
0x6f6493…b480
8 touches
6 conflicts
0x4637d742…d119
0x6f6493…b480
8 touches
6 conflicts
0x4953a725…2559
0x6f6493…b480
8 touches
6 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
6 conflicts on slot 0x16e8a2fe6f…3b0a38
Audit this contract →
← previous block·next block →recent activity