← previous blocknext block →recent activity
Analyzing
Block #106,809,933
28 transactions · 26 stateful · 2026-09-21 17:34:23 UTC
Parallelism
64/100
Blocked
65%
Avg conflicts / tx
2.14
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #106,809,933 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w08w39w413w114w115w516w118w219w320w421w522w627w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x25957369…c648
0x34b655…2a6f
12 touches
15 conflicts
0xdf6b3ac1…433c
0x34b655…2a6f
12 touches
15 conflicts
0xc638fb2a…1bab
0x34b655…2a6f
12 touches
15 conflicts
0xfcc8f826…7c5f
0x34b655…2a6f
10 touches
10 conflicts
0x24b2ba87…21ff
0x34b655…2a6f
10 touches
10 conflicts
0x932a9590…0b19
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
10 touches
10 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
21 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity