← previous blocknext block →recent activity
Analyzing
Block #105,748,789
32 transactions · 27 stateful · 2026-09-18 00:30:15 UTC
Parallelism
72/100
Blocked
59%
Avg conflicts / tx
1.38
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,748,789 · 32 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
2w03w16w08w09w010w111w112w213w314w115w216w118w320w421w522w623w724w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x335324b6…542f
0x34b655…2a6f
12 touches
15 conflicts
0x213b816c…a5e0
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0xe2a28bef…74d2
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb85
0x1b6862…e19c
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
15 conflicts on slot 0x335324b6b0…f1542f
Audit this contract →
← previous block·next block →recent activity