← previous blocknext block →recent activity
Analyzing
Block #105,852,447
37 transactions · 35 stateful · 2026-09-18 09:13:23 UTC
Parallelism
70/100
Blocked
66%
Avg conflicts / tx
2.14
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #105,852,447 · 37 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
1w02w13w24w35w46w58w614w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
18 touches
36 conflicts
0x382434ca…96b5
0x34b655…2a6f
12 touches
15 conflicts
0x3c9b10c1…d791
0x34b655…2a6f
10 touches
10 conflicts
0x48828733…fd48
0x34b655…2a6f
10 touches
10 conflicts
0x7a3d5e6f…7864
0x34b655…2a6f
10 touches
10 conflicts
0x9daafdf9…bb53
0x34b655…2a6f
10 touches
10 conflicts
0xa7923b81…93a5
0x34b655…2a6f
10 touches
10 conflicts
0xa7f7a563…4504
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
36 conflicts on slot 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity