← previous blocknext block →recent activity
Analyzing
Block #106,952,939
39 transactions · 36 stateful · 2026-09-22 05:34:12 UTC
Parallelism
64/100
Blocked
69%
Avg conflicts / tx
3.13
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #106,952,939 · 39 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w16w29w110w211w113w215w316w417w518w619w720w821w925w127w1028w1129w1230w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3eb48ea2…eef2
0x34b655…2a6f
26 touches
78 conflicts
0x61155067…cec4
0x34b655…2a6f
20 touches
45 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xcc844ab5…4c6d
0x34b655…2a6f
12 touches
15 conflicts
0x232b0b19…d946
0x34b655…2a6f
8 touches
6 conflicts
0x49b9fdd5…9c16
0x34b655…2a6f
8 touches
6 conflicts
0x5c89f4b3…9c08
0x34b655…2a6f
8 touches
6 conflicts
0x8d5fc820…1750
0x34b655…2a6f
6 touches
3 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
78 conflicts on slot 0x3eb48ea2b8…b6eef2
Audit this contract →
← previous block·next block →recent activity