← previous blocknext block →recent activity
Analyzing
Block #106,386,019
21 transactions · 20 stateful · 2026-09-20 05:59:49 UTC
Parallelism
76/100
Blocked
45%
Avg conflicts / tx
1.1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,386,019 · 21 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
1w02w13w14w25w06w17w216w217w318w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb0e974c4…b84d
0x34b655…2a6f
8 touches
6 conflicts
0xbcdd58ff…0711
0x34b655…2a6f
8 touches
6 conflicts
0xe1944aff…428b
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x64275949…d698
0x34b655…2a6f
8 touches
6 conflicts
0x9210e826…1414
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x961c0cd9…0937
0x34b655…2a6f
6 touches
3 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: Perpl
6 conflicts on slot 0xb0e974c47d…53b84d
Audit this contract →
← previous block·next block →recent activity