← previous blocknext block →recent activity
Analyzing
Block #106,953,886
19 transactions · 19 stateful · 2026-09-22 05:38:58 UTC
Parallelism
63/100
Blocked
37%
Avg conflicts / tx
1.16
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,953,886 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w27w38w412w014w515w618w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe07205ad…1ccd
0x34b655…2a6f
14 touches
21 conflicts
0x1c59817b…07e8
0x34b655…2a6f
10 touches
10 conflicts
0x23769ebc…c8ed
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
4 touches
1 conflict
0x6c60fbcf…8744
0x34b655…2a6f
4 touches
1 conflict
0xa9a9d0e0…4087
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: Perpl
21 conflicts on slot 0xe07205ada3…171ccd
Audit this contract →
← previous block·next block →recent activity