← previous blocknext block →recent activity
Analyzing
Block #106,809,874
26 transactions · 21 stateful · 2026-09-21 17:34:05 UTC
Parallelism
65/100
Blocked
48%
Avg conflicts / tx
1.23
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #106,809,874 · 26 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
1w02w14w26w313w314w317w420w521w622w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65b86b0a…1c53
0x34b655…2a6f
14 touches
21 conflicts
0x38594928…2c55
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x8725f80c…ff6d
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0x1b25f260…c429
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 0x65b86b0a1d…011c53
Audit this contract →
← previous block·next block →recent activity