← previous blocknext block →recent activity
Analyzing
Block #106,215,578
30 transactions · 26 stateful · 2026-09-19 15:42:02 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,215,578 · 30 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
1w06w17w08w09w115w218w320w321w422w023w124w225w328w129w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03a61e56…5d0f
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
8 touches
6 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0x8f13071b…959c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x24ed74ea…a3ff
0x34b655…2a6f
6 touches
3 conflicts
0x65e57979…e43d
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 0x03a61e5692…bc5d0f
Audit this contract →
← previous block·next block →recent activity