← previous blocknext block →recent activity
Analyzing
Block #106,164,724
18 transactions · 16 stateful · 2026-09-19 11:26:03 UTC
Parallelism
83/100
Blocked
25%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,164,724 · 18 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w111w012w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1be9b382…2a5e
0xe52b14…7230
6 touches
3 conflicts
0x1be9b382…2a60
0xe52b14…7230
6 touches
3 conflicts
0xf3ab898f…a814
0xe52b14…7230
6 touches
3 conflicts
0xf3ab898f…a816
0xe52b14…7230
6 touches
3 conflicts
0xf79df061…e005
0xe52b14…7230
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x67c1f465…38b3
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
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: 0xe52b1424…bb7230
3 conflicts on slot 0x1be9b38295…192a5e
Audit this contract →
← previous block·next block →recent activity