← previous blocknext block →recent activity
Analyzing
Block #105,852,401
47 transactions · 43 stateful · 2026-09-18 09:13:09 UTC
Parallelism
64/100
Blocked
72%
Avg conflicts / tx
2.68
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,852,401 · 47 txs across 17 waves · depth 17
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
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w48w211w515w617w118w224w828w929w1031w1134w1235w1342w1243w1344w1445w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbc8fb280…76a3
0x34b655…2a6f
16 touches
28 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
14 touches
21 conflicts
0xf97b1ece…fbfa
0x34b655…2a6f
14 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0x167cf3c0…cedd
0xd32edf…ff58
13 touches
21 conflicts
0x48828733…fd48
0x34b655…2a6f
12 touches
15 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 0xbc8fb28081…2176a3
Audit this contract →
← previous block·next block →recent activity