← previous blocknext block →recent activity
Analyzing
Block #106,215,457
23 transactions · 22 stateful · 2026-09-19 15:41:25 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.17
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,215,457 · 23 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
1w02w15w08w09w111w112w213w314w415w516w620w522w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3b84582…0ade
0x34b655…2a6f
14 touches
21 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
8 touches
6 conflicts
0x85eb1316…bb9e
0x34b655…2a6f
6 touches
3 conflicts
0x3fa1fac4…826c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3df0284b…8cd0
0x34b655…2a6f
6 touches
3 conflicts
0xe22ab637…7a8e
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
21 conflicts on slot 0xd3b8458246…f30ade
Audit this contract →
← previous block·next block →recent activity