← previous blocknext block →recent activity
Analyzing
Block #106,915,957
31 transactions · 26 stateful · 2026-09-22 02:28:03 UTC
Parallelism
74/100
Blocked
54%
Avg conflicts / tx
1.65
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,915,957 · 31 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w111w213w314w415w519w524w628w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x050d7a8a…67d0
0x34b655…2a6f
14 touches
21 conflicts
0xc57dc3c1…4444
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x46483cb1…e7ca
0x34b655…2a6f
8 touches
6 conflicts
0x4786839b…c29a
0x34b655…2a6f
8 touches
6 conflicts
0xd7ce7964…157e
0x34b655…2a6f
8 touches
6 conflicts
0x793aa64d…b09c
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
21 conflicts on slot 0x050d7a8aa8…3167d0
Audit this contract →
← previous block·next block →recent activity