← previous blocknext block →recent activity
Analyzing
Block #105,684,211
18 transactions · 18 stateful · 2026-09-17 19:05:15 UTC
Parallelism
61/100
Blocked
44%
Avg conflicts / tx
1.67
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,684,211 · 18 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
1w02w14w05w16w113w214w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xeb5b61a2…b2bc
0x34b655…2a6f
14 touches
21 conflicts
0x49890ced…6f23
0x34b655…2a6f
10 touches
10 conflicts
0x1584e21a…6642
0x34b655…2a6f
10 touches
10 conflicts
0x62406c85…e348
0x34b655…2a6f
8 touches
6 conflicts
0xe561281f…7569
0x34b655…2a6f
6 touches
3 conflicts
0x07d94be1…7fa8
0x34b655…2a6f
6 touches
3 conflicts
0xfa24929f…7992
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity