← previous blocknext block →recent activity
Analyzing
Block #105,848,384
22 transactions · 21 stateful · 2026-09-18 08:52:56 UTC
Parallelism
55/100
Blocked
57%
Avg conflicts / tx
1.68
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,848,384 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w08w110w211w312w413w514w615w716w817w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfce7dfe…5053
0x34b655…2a6f
14 touches
21 conflicts
0x11506b7a…d05e
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x7c51d9aa…af39
0x34b655…2a6f
8 touches
6 conflicts
0x0a6862d7…c311
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x42522e76…2592
0x34b655…2a6f
8 touches
6 conflicts
0xd17580f9…ece1
0x754704…b603
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 0xdfce7dfe53…c75053
Audit this contract →
← previous block·next block →recent activity