← previous blocknext block →recent activity
Analyzing
Block #105,922,212
42 transactions · 33 stateful · 2026-09-18 15:05:23 UTC
Parallelism
88/100
Blocked
58%
Avg conflicts / tx
0.98
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,922,212 · 42 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
1w02w14w26w08w09w010w111w113w214w316w421w223w124w226w327w328w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
10 touches
10 conflicts
0xd17580f9…ece1
0x754704…b603
10 touches
10 conflicts
0xe2dc3260…f50c
0x34b655…2a6f
8 touches
6 conflicts
0x5ef326ed…69dc
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x8b52b75c…8a0d
0xa6afd3…d132
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0002
0xf5b5f7…6d70
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
10 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity