← previous blocknext block →recent activity
Analyzing
Block #106,586,301
26 transactions · 24 stateful · 2026-09-20 22:47:51 UTC
Parallelism
58/100
Blocked
67%
Avg conflicts / tx
3.08
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #106,586,301 · 26 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w15w210w311w412w513w614w715w816w917w1022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6d5fe8e7…2071
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0xb654bd89…a83b
0x34b655…2a6f
18 touches
36 conflicts
0xe5eb3c33…0e3a
0x34b655…2a6f
14 touches
21 conflicts
0x53ca1284…cb2c
0x34b655…2a6f
10 touches
10 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
10 touches
10 conflicts
0xebf4a826…a80c
0x34b655…2a6f
8 touches
6 conflicts
0x1b25f260…c429
0x34b655…2a6f
8 touches
6 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
55 conflicts on slot 0x6d5fe8e75c…562071
Audit this contract →
← previous block·next block →recent activity