← previous blocknext block →recent activity
Analyzing
Block #106,224,246
28 transactions · 26 stateful · 2026-09-19 16:25:39 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
1.39
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,224,246 · 28 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
3w04w17w09w110w211w312w413w514w615w716w827w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x2f50c84a…3640
0x34b655…2a6f
14 touches
21 conflicts
0x3aca5bf5…48e7
0x34b655…2a6f
14 touches
21 conflicts
0x634015e1…0b09
0x34b655…2a6f
14 touches
21 conflicts
0x7499cc33…a306
0x34b655…2a6f
14 touches
21 conflicts
0x7eb3ae1e…a1a3
0x34b655…2a6f
14 touches
21 conflicts
0x88fc2a68…3918
0x34b655…2a6f
14 touches
21 conflicts
0x98dd86bb…1edb
0x34b655…2a6f
14 touches
21 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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity