← previous blocknext block →recent activity
Analyzing
Block #105,852,432
25 transactions · 24 stateful · 2026-09-18 09:13:18 UTC
Parallelism
72/100
Blocked
54%
Avg conflicts / tx
1.2
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,852,432 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w110w011w113w214w215w316w417w518w623w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1033ac83…3fc5
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x25180879…8191
0x34b655…2a6f
12 touches
15 conflicts
0x5b7e7f56…6848
0x34b655…2a6f
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0xab981df1…2941
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0xd98b3c10…67b8
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
21 conflicts on slot 0x1033ac838f…253fc5
Audit this contract →
← previous block·next block →recent activity