← previous blocknext block →recent activity
Analyzing
Block #105,644,083
38 transactions · 34 stateful · 2026-09-17 15:43:15 UTC
Parallelism
63/100
Blocked
74%
Avg conflicts / tx
2.45
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #105,644,083 · 38 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
1w02w13w24w05w36w311w212w114w117w118w219w320w322w423w524w627w428w529w631w732w833w936w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
22 touches
55 conflicts
0x7aad02c6…b979
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0xb5cddf91…0abf
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xa6661639…f0ef
0x34b655…2a6f
8 touches
6 conflicts
0xfac61869…a55e
0x1b6862…e19c
6 touches
3 conflicts
0x3f47b9cc…2bb0
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
55 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity