← previous blocknext block →recent activity
Analyzing
Block #106,215,464
23 transactions · 23 stateful · 2026-09-19 15:41:28 UTC
Parallelism
78/100
Blocked
39%
Avg conflicts / tx
0.83
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,215,464 · 23 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
1w02w03w16w08w19w213w114w215w316w418w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5313975…c5f1
0x34b655…2a6f
10 touches
10 conflicts
0x581b829b…9578
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x10522859…4a69
0x34b655…2a6f
6 touches
3 conflicts
0x2d071de0…c86e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x4ec9ff52…e6f7
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
10 conflicts on slot 0xa531397531…bcc5f1
Audit this contract →
← previous block·next block →recent activity