← previous blocknext block →recent activity
Analyzing
Block #105,575,373
31 transactions · 30 stateful · 2026-09-17 09:57:22 UTC
Parallelism
71/100
Blocked
37%
Avg conflicts / tx
1.1
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #105,575,373 · 31 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
1w02w13w04w19w010w111w215w316w417w518w619w720w830w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5ddc4a77…765e
0x34b655…2a6f
16 touches
28 conflicts
0x839459c3…729d
0x34b655…2a6f
12 touches
15 conflicts
0xe708c9f4…b505
0x34b655…2a6f
10 touches
10 conflicts
0x0463db49…5d05
0x34b655…2a6f
8 touches
6 conflicts
0xe3684e08…c96a
0x34b655…2a6f
8 touches
6 conflicts
0xf71016c7…5c7c
0x34b655…2a6f
6 touches
3 conflicts
0x42522e76…2592
0x34b655…2a6f
6 touches
3 conflicts
0x49890ced…6f23
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
28 conflicts on slot 0x5ddc4a7765…4b765e
Audit this contract →
← previous block·next block →recent activity