← previous blocknext block →recent activity
Analyzing
Block #105,549,943
35 transactions · 30 stateful · 2026-09-17 07:49:23 UTC
Parallelism
57/100
Blocked
60%
Avg conflicts / tx
3.49
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #105,549,943 · 35 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w39w410w511w612w713w814w915w1017w1118w1219w1320w1131w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e632c…e14c
0x34b655…2a6f
26 touches
78 conflicts
0xdac7e046…6ea7
0x34b655…2a6f
26 touches
78 conflicts
0x309f47c0…e1cf
0x34b655…2a6f
24 touches
66 conflicts
0x3b65c5ca…9f83
0x34b655…2a6f
24 touches
66 conflicts
0x40d6d1e9…131e
0x34b655…2a6f
24 touches
66 conflicts
0x6d5d1fb5…86a7
0x34b655…2a6f
24 touches
66 conflicts
0x7006165a…df17
0x34b655…2a6f
24 touches
66 conflicts
0xa7d3cb90…e1d9
0x34b655…2a6f
24 touches
66 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
78 conflicts on slot 0xfd4e632c76…e1e14c
Audit this contract →
← previous block·next block →recent activity