← previous blocknext block →recent activity
Analyzing
Block #106,282,340
23 transactions · 22 stateful · 2026-09-19 21:18:04 UTC
Parallelism
78/100
Blocked
41%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,282,340 · 23 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
2w03w14w06w112w213w214w315w420w121w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ba10aad…9bc5
0x34b655…2a6f
8 touches
6 conflicts
0x418e9dd6…5263
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x74372904…238a
0x34b655…2a6f
4 touches
1 conflict
0x85eb1316…bb9e
0x34b655…2a6f
4 touches
1 conflict
0xda18212c…b8b6
0x34b655…2a6f
4 touches
1 conflict
0x997aea7d…1b09
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
6 conflicts on slot 0x9ba10aada6…3c9bc5
Audit this contract →
← previous block·next block →recent activity