← previous blocknext block →recent activity
Analyzing
Block #105,856,781
26 transactions · 25 stateful · 2026-09-18 09:35:12 UTC
Parallelism
35/100
Blocked
72%
Avg conflicts / tx
5.08
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #105,856,781 · 26 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
4w05w16w28w310w211w312w413w514w615w716w817w918w1019w1120w1221w1322w1423w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
32 touches
120 conflicts
0x97e4c862…4419
0x34b655…2a6f
24 touches
66 conflicts
0x7c843949…1aa1
0x34b655…2a6f
20 touches
45 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x42522e76…2592
0x34b655…2a6f
10 touches
10 conflicts
0x92b49f44…ee4f
0x34b655…2a6f
10 touches
10 conflicts
0x9ff4ca89…6115
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 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
120 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity