← previous blocknext block →recent activity
Analyzing
Block #106,235,734
32 transactions · 29 stateful · 2026-09-19 17:23:32 UTC
Parallelism
72/100
Blocked
76%
Avg conflicts / tx
2.22
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,235,734 · 32 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x800bbaf8…b709
0x34b655…2a6f
16 touches
28 conflicts
0xca70df5d…41c1
0xd32edf…ff58
15 touches
28 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x26bb6db7…f863
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x482471ad…122f
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
28 conflicts on slot 0x800bbaf8ad…d8b709
Audit this contract →
← previous block·next block →recent activity